TelORB Set Up Files
Last updated: February 22, 2001
  Click to get to the TelORB Home Page
Note! Let the loading of this page come to a complete stop, to make the internal links work.

The file examples in this document are valid for TelORB R13.

This page contains examples of most of the files that are necessary for running a TelORB system and its belonging IO processors. The files in this example collection are fetched from TelORB system to14 (27-30 TelORB processors) and the same IP addresses as specified in the TelORB Guidelines page are valid.

The following TelORB and IO set up files are currently available:

General


TelORB system building files


JAMBALA system building files
created at LMC (valid for AD9)


Console windows and log files

 

IO processor files

General File Information               Back to Contents

Regarding the epct files, either include everything in one epct file or split
it up into several epct files for a better overview. The latter is used in these
guidelines.

o File for setting up the build environment with information about e.g. which AD
  or test bed to build from, as well as information about which epct files to be
  included when building the system:
  - Envsettings

o File that includes what name the TelORB system will get after the initial
  load.
  Also, the file contains information about the zone identity if the TelORB
  system is part of a network redundant system:
  - name.epct                 (NAME, ZONE)

o Files that include TelORB processor MAC addresses:
  - processor.epct            (ADDRESS)
  - dhcpd.pxe.conf
  - telorb.conf               (IO1 & IO2: /opt/telorb/etc/)
  - networkAddresses          (IO1: /opt/telorb/axe/loadingGroup01_1/)
                              (IO2: /opt/telorb/axe/loadingGroup01_2/)
                              (Automatically created at initial load)

o Files that include IP addresses:
  - telorbData.epct           (DorbIIOPHostName, DUMP_HOST_ID, ETHSW_ADDRESSES)
  - dhcpd.pxe.conf
  - hosts
  - ep_tftpd.conf

o Files that include processor allocations to pools (dependent on the number of
  TelORB processors):
  - processor.epct            (PROCESSOR)
  - netred.epct               (PROCESSOR)
  - demo.epct                 (PROCESSOR)
  - java.epct                 (PROCESSOR)
  - omed.epct                 (PROCESSOR)
  - pools.epct                (PROCESSOR)

o Files that are dependent on the number of TelORB processors (also see previous
  item, i.e. processor allocations to pools):
  - dhcpd.pxe.conf            (It is OK to include more processors than what
                               physically exist in the TelORB system. This is
                               however not valid for the processor.epct file)
  - start_services            (/opt/telorb/tools/bin/STSsw 7 7001 -log &)
                              (/opt/telorb/tools/bin/DicosSyslogClient -L -m io1
                               134.138.xx.101-107 > /opt/telorb/syslog &)
  - README.txt                (For starting consolelogs, located at e.g.
                               /home/telorb/toX/consolelogs on e.g. a local WS)

o File that includes settings depending on the number of cabinets in the system:
  - telorbData.epct           (ETHSW_ADDRESSES)

o Files that include information about which software IDPs/IDGs that are being
  used:
  - telorb.epct               (SOFTWARE)
  - netred.epct               (SOFTWARE)
  - demo.epct                 (SOFTWARE)
  - java.epct                 (SOFTWARE)
  - omed.epct                 (SOFTWARE)
  - axmp.epct                 (SOFTWARE)
  - servicePlatform.epct      (SOFTWARE)

o Files that include initial data settings:
  - telorbData.epct           (INITIAL DATA)
  - servicePlatform.epct      (INITIAL DATA)

o File that includes information about where to put backups and where to reload
  from:
  - ep_tftpd.conf

File Envsettings, located at e.g.
/home/dicostest/tosFiles/to14/ad13.1/
               Back to Contents

Example of file contents:
# For ADs
set Owndir=`pwd`
cd /ipims_dicos/ipims_dicos10/dists/TelORB-AD13.1/
source setup.csh
cd $Owndir

# For test beds
# source /ipims_dicos/BS2/tbAD13.1/IP_CONF_INFO/EnvSettings

# For ADs and test beds
setenv EP_WORKSPACE `pwd`/epws
setenv DICOS_FILESYSTEM_ROOT `pwd`/axe

# Build with TelORB_Base + NetRed + DemoApp + DemoApp2000 + JavaApp + HLR + AC + SCP (Omed and AXmp excluded)
alias build 'epct -t i486 -vFc -f loadingGroup01_1 -f loadingGroup01_2 -d ../axe name.epct ../../epct/ad13/telorbDataGeneral.epct telorbDataLocal.epct telorb.epct processor.epct netred.epct demo.epct demo2000.epct java.epct servicePlatform.epct pools.epct'

# Print epconfig settings
epconfig l -v

Comments:

File name.epct, located at e.g.
/home/dicostest/tosFiles/to14/ad13.1/
               Back to Contents

Example of file contents:
NAME to14_ad131_initial_zone1;
ZONE 1;

Comments:

File telorb.epct, located at e.g.
/home/dicostest/tosFiles/to14/ad13.1/
               Back to Contents

Example of file contents:
SOFTWARE         
        IDP/MD14,       // Dicos_IDP
        IDP/MD16,       // Ethernet_IDP
	IDP/D13,	// IntelPcProcessorManagement_IDP, For target machine
        IDP/DUO2,       // Net_IDP, To show load on processors
        IDP/MD18,       // Java_IDP, Optional
        IDP/D3,         // KnuerrRms_IDP, Optional
        IDP/MD1;        // DbConsistency_IDP, Test IDP for MdpSynchCheck, Optional

Comments:

File telorbDataGeneral.epct, located at e.g.
/home/dicostest/tosFiles/epct/ad13/
               Back to Contents

Example of file contents:
INITIAL DATA

############################################################################
#                                                                          #
# This file does not contain any site dependent data.                      #
# Thus, the local TelORB data file has to be read after this file, i.e.    #
# epct ... ../../epct/ad13/telorbDataGeneral.epct telorbDataLocal.epct ... #
#                                                                          #
# Note! DorbIIOPHostName and ETHSW_ADDRESSES are not set in this file.     #
#                                                                          #
############################################################################

# All comments for initial data must start with #
# Initial data needed for a customer site


# Time service
#
# The IP and port of the NTP server (port = 123 is default) 
# This should be the NTP server used by the site
NTP_SERVER_PORT = 123

# TIME_TZ_OFFSET is the Local Time Zone offset in hours.
# Because only positive numbers can be given here the number is adjusted:
# intOffset = (TIME_TZ_OFFSET > 12) ? TIME_TZ_OFFSET-24 : TIME_TZ_OFFSET;
TIME_TZ_OFFSET = 1

# Daylight Saving Time dates.
# This array consists of pairs: YYYYMMDDHH,offset
# The date is the non DST adjusted local (not UTC) time when the
# local time is altered. The offset is in hours. On the northen
# hemisphere you might set offset=1 in Mars and restore to 
# offset=0 in October.
TIME_DST_DATES = ( 2000032602,1,  2000102902,0)


#
# Purge Lazys
# 
DdbLazyPurgeInterval = 60000               # default value 
#
# Explanation: 
# The period in milliseconds for the lazy-purger.
# If a database object is accessed on a processor to which
# the object is not replicated, a cached copy is installed.
# These cached copies are called "lazy copies" for
# historical reasons. 
#
# The lazy-purger is a garbage collector of such cached copies.
# 
# If the period for the lazy copy purger is too high then the processor
# may, in a worst-case scenario, run-out of memory. 
# However, before running out of memory, the processor would have problems 
# with repeatedly having to expand the table holding the lazy-copies. 
# If this happens you will see a lot of warning messages on
# the processor's console.
# 
# Value-range: '0', or the number of milliseconds for the period.
# 
# Explanation of values:
# A value of '0' is special in that it will cause the
# lazy-purger to be idle (i.e. never run).
# A value below 15,000 (every 15 seconds) should be avoided.
# The default value of 60,000 (once a minute) works well for
# most systems. 
# The exception would be a system that is generating a lot 
# of lazy copies, due to (for example) a bulk loading phase.
#

#
# Maximum number of objects per processor (including replication).
#
DdbRecordTabMasterSize = 1650000

# Explanation:
# This value is the result of a calculation ((((a * b) * 2) *2) / (c-1)) * 1.1)
# where:
# a = the maximum number of subscribers when the system is fully 
# configured for this number of processors
# b = the number of POT (objects) per subscriber)
#
# The result of multiplying a by b is then doubled to allow for the existence
# of replicas. That result is then doubled again to allow for backups. The
# result is then divided by c-1
# c = the number of processors in the system.
#
# one is subtracted from c to compensate for the fact that one processor could 
#    be out of service. This gives a margin for reconfiguration. If the loaders are 
#    not used for normal traffic then they should not be included as processors 
#    when calculating the value of c.
# 
# The whole result is then increased by 10% (multiplied by 1.1) to give a safety
# margin.
#
# Check memory cost afterwards. It is 16B x DdbRecordTabMasterSize
#
# Example: 1,000,000 subscribers each consisting of 10 POTs (objects) on a 28 
# processor system (where the loaders are used for normal traffic) gives
# (1,000,000 * 10 * 2 * 2) / (28 - 1) rounded is 1,500,000 multiplied by 1.1 
# gives 1,650,000
#
# Values must be in the range 100,000 to (max depends on available memory in
# the processor).
#
# A low value such as 100,000 means that there are approximately 
# 25,000 objects per processor, not counting replicas, and is therefore usually
# used for Vegas, or if you have large objects (max object size is
# 32KB) or limited memory. 
#
# The table can expand dynamically, but this causes severe 
# performance problems. If the table is larger than 200,000
# when it expands dynamically then the processor will effectively crash.


# Maximum number of lazy copies expected per processor. 
DdbRecordTabLazySize = 100000 
#
# Explanation: 
# The size, in number of entries, for the table that holds lazy-copies. 
# If a database object is accessed on a processor to which
# the object is not replicated, a cached copy is installed.
# These cached copies are called "lazy copies" for
# historical reasons.
#
# The lazy-purger is a garbage collector of such
# cached copies. The table should be large enough to
# accommodate the lazy copies created in the period between 
# purger runs.
#
# If the table is too small then the processor will be forced 
# to repeatedly expand the table. 
# The table can expand dynamically but this can cause performance 
# problems and memory fragmentation.
# 
# Value-range: 0 - 500,000
# The size should be adjusted to approximately 25% larger
# than the maximum number of lazy copies typically created in 
# the period between purger runs. 
# Note that if the same object is accessed several
# times, only one cached copy is created.
# 
# Explanation of values:
# A value of '0' means you don't expect to ever access
# non-local objects on any processor. 
# The default value of 100,000 (1.5 MB) should be sufficient
# for most systems with the purger running every 60 seconds.
# Each table entry costs 16 bytes of memory.


# Load Module Size
#
# The maximum load module size for data backup in bytes
# excluding headers. 
DdbBackupLoadmoduleSectionSize = 0x3D0900
#
#Explanation:
# 
# A DB backup load module consists of three parts,
# the LoadModuleHeader, the DBbackupHeader and 
# a data sector for the contained data.
# DdbBackupLoadmoduleSectionSize sets the
# maximum allowed size for the data sector within a 
# DB backup load module before compression. 
#
# Values: Default is 1 MByte (0xF4240) intended for Vega,
# for target systems 4 MByte (0x3D0900) is recommended 
#
# By increasing the maximum allowed section size it is 
# possible to limit the number of created DB backup 
# files/load modules per MDP (and Distribution Unit). 

# The number of MDP objects (DUs with POTs) that can be in the table,
# rounded upwards with 25%
DdbMdpTabSize = 10000
#
# Explanation:
# Each key-introducing POT will have a number of MDPs (Master Data 
# Partitions) equal in number to the DU-limit for that POT's DUT. 
# If more than one key-introducing POT is associated with one DUT, 
# then each has to be counted.
#
# The DdbMdpTabSize should be set to be 25% larger than 
# the sum of all MDPs. Dicos itself has approximately 150 MDPs.
# For any given system, one should take into account the 
# applications that will run on that system, or be likely
# to be installed on the system. 
# The table can expand dynamically but this can cause performance 
# problems and memory fragmentation.
# 
# Value-range: 500 - 50,000. Default 10,000
# 
# Explanation of values:
# The default value of 10,000 was designed for the Jambala
# HLR application: a system designed to scale up to be very large,
# thus having large distribution limits. 
# The largest allowed distribution limit is currently 1024.

#
# DorbIIOPHostName
#
# The Processors where the IIOP gateways are located at the site.
# Use different processors for each net. The processors must 
# belong to the DicosPlgLoaderPool.
# The IP addresses must be those local for the site
# Replace these addresses with your local IP addresses
# DorbIIOPHostName = "TelorbProc1:TelorbProc2"

#
# DorbIIOPPort and DorbIIOPGwSlavePort
#
# The TCP/IP ports for the IIOP gateway master and slave for TelORB
DorbIIOPPort = 30330 #default value
DorbIIOPGwSlavePort = 30600 #default value

#
# IOR_Print
#
# If set to 1 all CORBA system resource objects will print their IORs 
# to the console at start time. Default is 0.
IOR_PRINT = 0

#
# IPC Overload Levels
#
# Level where messages to not connected ports do not get through 
IpcOverloadRejectLevels = (1000, 2000, 100000)
# Level where overload warning is sent for connected ports
IpcOverloadWarningLevels = (1000, 2000, 100000)
# Level where messages are aborted for connected ports
IpcOverloadAbortLevels = (2000, 4000, 100000)

#
# Dump generation
#
# Description of the dump tool configuration and usage
#
# The `dumpd' tool should be used to retrieve dumps on a
# Unix host. Type `dumpd -h' to get help for `dumpd'.
# The dump files are mostly ASCII-text (for now) and are stored in the
# directory where `dumpd' is started. The filenames are
#
# DicosTextDump-n For Capsule dumps
# DicosProcessorTextDump-n For Processor dumps
# DicosJavaDump-n The dump from a crashed Java process
# containing the stack trace.
# DicosSyslogDump-n The syslog printouts than have not yet 
# been sent to the IO-machine when a 
# Processor crash occurs. This is not a 
# text file.
#
# Where `n' is an index.
# The Text, Processor, and Java dump files are analyzed with the 
# `epelfaddr_dmp' script. The Syslog Dump (since it is not a text file) 
# cannot use the script and must be analyzed with the 
# DicosSyslogClient program.

#
# DUMP_MODE
#
# bit 0 - Console dump
# bit 1 - Remote Capsule Dump
# bit 2 - Remote Processor Dump
# `0' means OFF, '1' means "ON", to turn everything on set DUMP_MODE = 7
DUMP_MODE = 7

#
# DUMP_HOST_PORT
#
# The UDP-port that `dumpd' listens on.
# The default port for `dumpd' is 5556.
DUMP_HOST_PORT = 5556

#
#DUMP GATEWAYS
#
# IP-gateways to the `DUMP_HOST_ID'
# (these should be omitted if gateways are not needed,
# i.e. if system and dumphost are not on the same net)
#DUMP_GATEWAY_1 = (Gateway_1_IPaddress)
#                use comma, not dot for this IP address
#DUMP_GATEWAY_2 = (Gateway_2_IPaddress)
#                use comma, not dot for this IP address

#
# DUMP_DRIVER
#
# The name of the driver for remote dumps, should always be "DumpDriverTftp"
# for now.
DUMP_DRIVER = "DumpDriverTftp"
#
# End of dump tool stuff

## INITIAL DATA for the optional Hardware Alarms Collector
## (KnuerrRms_IDP). If used remove the comments.
## Knuerr HW alarm
##
## IP Address
## The IP address for the Hardware Alarms Collector (Knuerr RMS)
## Replace this IP address with the IP address of your Hardware 
## Alarms Collector.
RMS_IP_ADDRESS = "RMS"
##
## Number of Cabinets
## RMS_NO_CABINET_B = 0 #the system consists of two cabinets
## RMS_NO_CABINET_B = 1 #the system consists of one cabinet
RMS_NO_CABINET_B = 1
##
## Maximum Temperature
## The temperature (in degrees Celsius) at which the RMS will start to report
## temperature alarms. Range 0 to 99. Default is 55.
RMS_MAX_TEMP = 60
##
## Poll interval
## The interval (in milliseconds) between polls of the Knuerr RMS by TelORB.
## Default is 15,000 (15 seconds)
RMS_POLL_INTERVAL = 15000

## INITIAL DATA for the optional Java IDP, if used remove the comments
## Java Virtual Machine (JVM)
## To avoid lack of memory in the JVM, use the following settings.
## The sizes are in Mega-bytes. Default values are 4Mbytes for the JVM, and
## 8Mbytes for the entire JVM-Capsule.
## JAVA_HEAP - Is the size available for Java-code and Java-data.
## The size must be big enough to hold all your (un-packed)
## application classes, and all data (objects).
## Maximum value is 27Mbytes.
## JAVA_CAPSULE_HEAP - Is OPTIONAL. If not specified, it is set to
## JAVA_HEAP+4Mbytes. The size must be big enough to hold the
## entire JAVA_HEAP, plus the JVM-code and internal data,
## AND all JavaJar-LMs that you load initially.
## Maximum value is 31Mbytes.
## The JavaJar-LMs are temporary stored on the Capsule-heap until the JVM
## is completely started.
#JAVA_HEAP = 4 # default value, see explanation above for your own value
JAVA_HEAP = 24 # adaptation to the current application
JAVA_CAPSULE_HEAP = 31

##
## To run on the target hardware, the following values are recommended 
## for use with HotSpot
##
## LMReciever and LMDistributor are processes having memory areas reserved
## on each processor as LMR_buffer_size and LMD_buffer_size.
## These buffers should be big enough to contain the largest filesize of any
## of the LMs used in the system. 
## During loading, memory areas are reserved in the kernel on each processor
## for BOOT as BOOT_buffer_size.
## This buffer has to be as big as both the LMReciever and LMDistributor
## processes together.
## At present the largest known filesize is 6Mb, which - with extra margin -
## is set to 8Mb for LMR_buffer_size and LMD_buffer_size. 
## The BOOT_buffer_size is set to 16Mb.
#
BOOT_buffer_size = 16000000
LMR_buffer_size = 8000000
LMD_buffer_size = 8000000

## INITIAL DATA for the optional NetRed IDP, if used remove the comments
##
##Definition:
##The DdbExtSynchNoOfProcesses is the maximum number of 
## DdbDynamicDbSynchC processes on each processor that are engaged in 
## synchronizing the database from an external backup.
##
##Dimensioning guidelines:
##Each process reads one backup file at a time. Thus the need for file
##descriptors in the file server increases with the number of processes. The
##formula is roughly
## fileDescrCount = processorCount * DdbExtSynchNoOfProcesses * 2
##
##Thus the DdbExtSynchNoOfProcesses should not be too high. E.g. on a 28
##processor system, 10 processes on each processor would yield a load of 560
##file descriptors which currently does not work.
##
##If the DdbExtSynchNoOfProcesses is set too low, the external synch takes
##longer time than necessary. Experience has it that there is limited use to
##put it higher than at 5 processes even on a smaller system (6 processors)
##because at that level the file system is already saturated with requests.
##Also, the DdbDynamicDbSynchC processes compete fairly well with the
##MirroringProcesses.
##
##The default is good enough for most installations.
##
DdbExtSynchNoOfProcesses = 5 # default value

# DNS
SymbolicAddress_0 = "localhost:localhost.localdomain"
NumericAddress_0  = "127.0.0.1"
SymbolicAddress_1 = "DNS_SERVERS"
NumericAddress_1  = "134.138.226.13:134.138.201.17"

ENDDATA

ENVIRONMENT DATA

//
// ETHSW_POLL_INTERVAL
//
// This is the interval (in milliseconds) between polls to see whether
// the switches can be reached. Defaults to 15,000 (15 seconds).
ETHSW_POLL_INTERVAL = "15000"

//
// ETHSW_CFG_INTERVAL 
//
// This interval specifies (in milliseconds) how often TelORB checks the 
// Environment data for changes. TelORB is not notified automatically 
// when the operator changes the environment, so it has to be checked 
// regularly. Since checking the environment data is a slow operation it 
// should not be done frequently. The default is 1,800,000 (30 minutes): 
// we suggest that you keep it. The minimum value is 10,000.
ETHSW_CFG_INTERVAL = "1800000"

//
// ETHSW_ADDRESSES 
//
// This is a comma separated list of IP-addresses of the
// switches to supervise. The first will be instance "A" in the alarms,
// the second "B" and so on. Replace the addresses below with those valid
// for your site.
// ETHSW_ADDRESSES = "EthSwitch1,EthSwitch2,EthSwitch3,EthSwitch4"


////Environment DATA for the optional AXmp SS7 terminator
//// If used remove the comments.
////
//// AXMP_POLL_INTERVAL -
////
//// The AXmps are polled rather than being checked with SNMP traps.
//// This variable specifies the poll interval in milliseconds. 
//// The default is 20,000, i.e. every 20 seconds. 
////
//AXMP_POLL_INTERVAL = "20000"
////
//// AXMP_ADDRESSES
////
//// This is a list of symbolic names for the AXmps to supervise. 
//// A UDP port can be specified, and should be separated from the 
//// name with a colon . 
////
//// The default port is 161, which is the standard port for SNMP.
////
//AXMP_ADDRESSES = "AXMP0:9977,AXMP1:9977"
////
//// AXMP_HIGH_TEMP
////
//// The temperature in degrees Celsius at which the temperature alarm
//// is generated. The default is 50 degrees.
////
//AXMP_HIGH_TEMP = "50"
////
//// AXMP_VOLTAGE_INTERVAL
////
//// The accepted CPU core voltage range specified in 1/10 Volts, 
//// i.e. 25 means 2.5 Volts. Default value is 24-31 (i.e. 2.4 to 3.1 Vols).
//// If the voltage drops below, or peaks above, this range, the
//// appropriate voltage low/voltage high alarm is generated.
////
//AXMP_VOLTAGE_INTERVAL = "24-33"

ENDDATA

Comments: Explanations:

File telorbDataLocal.epct, located at e.g.
/home/dicostest/tosFiles/to14/ad13.1/
               Back to Contents

Example of file contents:
INITIAL DATA

############################################################################
#                                                                          #
# This file only contains site dependent TelORB data.                      #
# Thus, the general TelORB data file has to be read before this file, i.e. #
# epct ... ../../epct/ad13/telorbDataGeneral.epct telorbDataLocal.epct ... #
#                                                                          #
############################################################################

#
# DorbIIOPHostName
#
# The Processors where the IIOP gateways are located at the site.
# Use different processors for each net. The processors must 
# belong to the DicosPlgLoaderPool.
# The IP addresses must be those local for the site
# Replace these addresses with your local IP addresses
DorbIIOPHostName = "134.138.57.101:134.138.58.102"

ENDDATA

ENVIRONMENT DATA

//
// ETHSW_ADDRESSES 
//
// This is a comma separated list of IP-addresses of the
// switches to supervise. The first will be instance "A" in the alarms,
// the second "B" and so on. Replace the addresses below with those valid
// for your site.
ETHSW_ADDRESSES = "134.138.57.20,134.138.58.20,134.138.57.21,134.138.58.21"

ENDDATA

File processor.epct, located at e.g.
/home/dicostest/tosFiles/to14/ad13.1/
               Back to Contents

Example of file contents:
PROCESSOR Processor1 
        INITIAL
        TARGET i486 
        TYPE IntelPc 
        LOADER 
        ADDRESS "00:30:f7:00:c1:bd 00:a0:a5:12:13:88"
        IN DicosCommonPool,DicosPlgLoaderPool,DicosDbReplicaPool,DicosQnPool;

PROCESSOR Processor2 
        TARGET i486 
        TYPE IntelPc
        LOADER
        ADDRESS "00:30:f7:00:c7:65 00:a0:a5:12:11:34" 
        IN DicosCommonPool,DicosPlgLoaderPool,DicosDbReplicaPool,DicosQnPool;

PROCESSOR Processor3 
        TARGET i486 
        TYPE IntelPc 
        ADDRESS "00:30:f7:00:c7:8f 00:a0:a5:12:17:d3" 
        IN DicosCommonPool;

PROCESSOR Processor4 
        TARGET i486 
        TYPE IntelPc 
        ADDRESS "00:30:f7:00:c1:e9 00:a0:a5:12:11:35" 
        IN DicosCommonPool;

PROCESSOR Processor5 
        TARGET i486 
        TYPE IntelPc 
        ADDRESS "00:30:f7:00:c1:dc 00:a0:a5:12:11:4a" 
        IN DicosCommonPool;

PROCESSOR Processor6 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c7:69 00:a0:a5:12:11:15" 
	IN DicosCommonPool;

PROCESSOR Processor7 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c1:eb 00:a0:a5:12:11:49" 
	IN DicosCommonPool;

PROCESSOR Processor8 
        TARGET i486 
        TYPE IntelPc 
        ADDRESS "00:30:f7:00:c7:b0 00:a0:a5:12:18:51" 
        IN DicosCommonPool;

PROCESSOR Processor9 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c1:fc 00:a0:a5:12:13:7c" 
        IN DicosCommonPool;

PROCESSOR Processor10 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c2:28 00:a0:a5:12:11:4c" 
	IN DicosCommonPool;

PROCESSOR Processor11 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c1:c8 00:a0:a5:12:13:a6" 
	IN DicosCommonPool;

PROCESSOR Processor12 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c2:1f 00:a0:a5:12:0f:4e" 
	IN DicosCommonPool;

PROCESSOR Processor13 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c1:bc 00:a0:a5:12:13:a7" 
	IN DicosCommonPool;

PROCESSOR Processor14 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c1:b3 00:a0:a5:12:14:4e" 
	IN DicosCommonPool;

PROCESSOR Processor15 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c2:17 00:a0:a5:12:13:9c" 
	IN DicosCommonPool;

PROCESSOR Processor16 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c1:f8 00:a0:a5:12:0f:62" 
        IN DicosCommonPool;

PROCESSOR Processor17 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c7:7d 00:a0:a5:12:18:4a" 
	IN DicosCommonPool;

PROCESSOR Processor18 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c2:1b 00:a0:a5:12:13:a3" 
	IN DicosCommonPool;

PROCESSOR Processor19 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c2:00 00:a0:a5:12:13:96" 
	IN DicosCommonPool;

PROCESSOR Processor20 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c1:da 00:a0:a5:12:13:93" 
	IN DicosCommonPool;

PROCESSOR Processor21 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c2:0d 00:a0:a5:12:13:a5" 
	IN DicosCommonPool;

PROCESSOR Processor22 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c1:a6 00:a0:a5:12:13:92" 
	IN DicosCommonPool;

PROCESSOR Processor23 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c1:b1 00:a0:a5:12:11:69" 
	IN DicosCommonPool;

PROCESSOR Processor24 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c1:a2 00:a0:a5:12:13:94" 
	IN DicosCommonPool;

PROCESSOR Processor25 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c1:b0 00:a0:a5:12:14:17" 
	IN DicosCommonPool;

PROCESSOR Processor26 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c1:db 00:a0:a5:12:13:c1" 
	IN DicosCommonPool;

PROCESSOR Processor27 
	TARGET i486 
	TYPE IntelPc 
	ADDRESS "00:30:f7:00:c1:d7 00:a0:a5:12:14:16" 
	IN DicosCommonPool;

Comments:

File netred.epct, located at e.g.
/home/dicostest/tosFiles/to14/ad13.1/
               Back to Contents

Example of file contents:
SOFTWARE
	IDP/D2;		// NetRed_IDP, Optional

PROCESSOR Processor1 ALSO IN DicosNetRedPool,DicosNetRedConnectPool;
PROCESSOR Processor2 ALSO IN DicosNetRedPool,DicosNetRedConnectPool;
PROCESSOR Processor3 ALSO IN DicosNetRedPool;
PROCESSOR Processor4 ALSO IN DicosNetRedPool;
PROCESSOR Processor5 ALSO IN DicosNetRedPool;
PROCESSOR Processor6 ALSO IN DicosNetRedPool;
PROCESSOR Processor7 ALSO IN DicosNetRedPool;
PROCESSOR Processor8 ALSO IN DicosNetRedPool;
PROCESSOR Processor9 ALSO IN DicosNetRedPool;
PROCESSOR Processor10 ALSO IN DicosNetRedPool;
PROCESSOR Processor11 ALSO IN DicosNetRedPool;
PROCESSOR Processor12 ALSO IN DicosNetRedPool;
PROCESSOR Processor13 ALSO IN DicosNetRedPool;
PROCESSOR Processor14 ALSO IN DicosNetRedPool;
PROCESSOR Processor15 ALSO IN DicosNetRedPool;
PROCESSOR Processor16 ALSO IN DicosNetRedPool;
PROCESSOR Processor17 ALSO IN DicosNetRedPool;
PROCESSOR Processor18 ALSO IN DicosNetRedPool;
PROCESSOR Processor19 ALSO IN DicosNetRedPool;
PROCESSOR Processor20 ALSO IN DicosNetRedPool;
PROCESSOR Processor21 ALSO IN DicosNetRedPool;
PROCESSOR Processor22 ALSO IN DicosNetRedPool;
PROCESSOR Processor23 ALSO IN DicosNetRedPool;
PROCESSOR Processor24 ALSO IN DicosNetRedPool;
PROCESSOR Processor25 ALSO IN DicosNetRedPool;
PROCESSOR Processor26 ALSO IN DicosNetRedPool;
PROCESSOR Processor27 ALSO IN DicosNetRedPool;

File demo.epct, located at e.g.
/home/dicostest/tosFiles/to14/ad13.1/
               Back to Contents

Example of file contents:
SOFTWARE
	IDP/DEA9990;	// DemoApp_IDP, Optional

PROCESSOR Processor1 ALSO IN TrafficGeneratorPool;
PROCESSOR Processor2 ALSO IN TrafficGeneratorPool;
PROCESSOR Processor3 ALSO IN ApplicationPool;
PROCESSOR Processor4 ALSO IN ApplicationPool;
PROCESSOR Processor5 ALSO IN ApplicationPool;
PROCESSOR Processor6 ALSO IN ApplicationPool;
PROCESSOR Processor7 ALSO IN ApplicationPool;
PROCESSOR Processor8 ALSO IN ApplicationPool;
PROCESSOR Processor9 ALSO IN ApplicationPool;
PROCESSOR Processor10 ALSO IN ApplicationPool;
PROCESSOR Processor11 ALSO IN ApplicationPool;
PROCESSOR Processor12 ALSO IN ApplicationPool;
PROCESSOR Processor13 ALSO IN ApplicationPool;
PROCESSOR Processor14 ALSO IN ApplicationPool;
PROCESSOR Processor15 ALSO IN ApplicationPool;
PROCESSOR Processor16 ALSO IN ApplicationPool;
PROCESSOR Processor17 ALSO IN ApplicationPool;
PROCESSOR Processor18 ALSO IN ApplicationPool;
PROCESSOR Processor19 ALSO IN ApplicationPool;
PROCESSOR Processor20 ALSO IN ApplicationPool;
PROCESSOR Processor21 ALSO IN ApplicationPool;
PROCESSOR Processor22 ALSO IN ApplicationPool;
PROCESSOR Processor23 ALSO IN ApplicationPool;
PROCESSOR Processor24 ALSO IN ApplicationPool;
PROCESSOR Processor25 ALSO IN ApplicationPool;
PROCESSOR Processor26 ALSO IN ApplicationPool;
PROCESSOR Processor27 ALSO IN ApplicationPool;

File demo2000.epct, located at e.g.
/home/dicostest/tosFiles/to14/ad13.1/
               Back to Contents

Example of file contents:
SOFTWARE
	IDP/DEM101;	// Demo2_IDP, Optional

PROCESSOR Processor1 ALSO IN De2CoordPool;
PROCESSOR Processor2 ALSO IN De2CoordPool;
PROCESSOR Processor3 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor4 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor5 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor6 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor7 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor8 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor9 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor10 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor11 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor12 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor13 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor14 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor15 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor16 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor17 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor18 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor19 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor20 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor21 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor22 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor23 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor24 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor25 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor26 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;
PROCESSOR Processor27 ALSO IN De2TGPool,De2DisPool,De2SubPool,De2PopPool;

File java.epct, located at e.g.
/home/dicostest/tosFiles/to14/ad13.1/
               Back to Contents

Example of file contents:
SOFTWARE
	IDP/D1;		// JavaDemo_IDP, Optional

PROCESSOR Processor1 ALSO IN JavaDemoAppPool;
PROCESSOR Processor2 ALSO IN JavaDemoAppPool;
PROCESSOR Processor3 ALSO IN JavaDemoTGPool;
PROCESSOR Processor4 ALSO IN JavaDemoTGPool;
PROCESSOR Processor5 ALSO IN JavaDemoAppPool;
PROCESSOR Processor6 ALSO IN JavaDemoAppPool;
PROCESSOR Processor7 ALSO IN JavaDemoAppPool;
PROCESSOR Processor8 ALSO IN JavaDemoAppPool;
PROCESSOR Processor9 ALSO IN JavaDemoAppPool;
PROCESSOR Processor10 ALSO IN JavaDemoAppPool;
PROCESSOR Processor11 ALSO IN JavaDemoAppPool;
PROCESSOR Processor12 ALSO IN JavaDemoAppPool;
PROCESSOR Processor13 ALSO IN JavaDemoAppPool;
PROCESSOR Processor14 ALSO IN JavaDemoAppPool;
PROCESSOR Processor15 ALSO IN JavaDemoAppPool;
PROCESSOR Processor16 ALSO IN JavaDemoAppPool;
PROCESSOR Processor17 ALSO IN JavaDemoAppPool;
PROCESSOR Processor18 ALSO IN JavaDemoAppPool;
PROCESSOR Processor19 ALSO IN JavaDemoAppPool;
PROCESSOR Processor20 ALSO IN JavaDemoAppPool;
PROCESSOR Processor21 ALSO IN JavaDemoAppPool;
PROCESSOR Processor22 ALSO IN JavaDemoAppPool;
PROCESSOR Processor23 ALSO IN JavaDemoAppPool;
PROCESSOR Processor24 ALSO IN JavaDemoAppPool;
PROCESSOR Processor25 ALSO IN JavaDemoAppPool;
PROCESSOR Processor26 ALSO IN JavaDemoAppPool;
PROCESSOR Processor27 ALSO IN JavaDemoAppPool;

File omed.epct, located at e.g.
/home/dicostest/tosFiles/to14/ad13.1/
               Back to Contents

Example of file contents:
SOFTWARE
	IDP/Omed;	// Omed_IDP, Optional

PROCESSOR Processor1 ALSO IN OmedWorkPool;
PROCESSOR Processor2 ALSO IN OmedWorkPool;
PROCESSOR Processor3 ALSO IN OmedWorkPool;
PROCESSOR Processor4 ALSO IN OmedWorkPool;
PROCESSOR Processor5 ALSO IN OmedWorkPool;
PROCESSOR Processor6 ALSO IN OmedGeneratorPool;
PROCESSOR Processor7 ALSO IN OmedGeneratorPool;
PROCESSOR Processor8 ALSO IN OmedWorkPool;
PROCESSOR Processor9 ALSO IN OmedWorkPool;
PROCESSOR Processor10 ALSO IN OmedWorkPool;
PROCESSOR Processor11 ALSO IN OmedWorkPool;
PROCESSOR Processor12 ALSO IN OmedWorkPool;
PROCESSOR Processor13 ALSO IN OmedWorkPool;
PROCESSOR Processor14 ALSO IN OmedWorkPool;
PROCESSOR Processor15 ALSO IN OmedWorkPool;
PROCESSOR Processor16 ALSO IN OmedWorkPool;
PROCESSOR Processor17 ALSO IN OmedWorkPool;
PROCESSOR Processor18 ALSO IN OmedWorkPool;
PROCESSOR Processor19 ALSO IN OmedWorkPool;
PROCESSOR Processor20 ALSO IN OmedWorkPool;
PROCESSOR Processor21 ALSO IN OmedWorkPool;
PROCESSOR Processor22 ALSO IN OmedWorkPool;
PROCESSOR Processor23 ALSO IN OmedWorkPool;
PROCESSOR Processor24 ALSO IN OmedWorkPool;
PROCESSOR Processor25 ALSO IN OmedWorkPool;
PROCESSOR Processor26 ALSO IN OmedWorkPool;
PROCESSOR Processor27 ALSO IN OmedWorkPool;

File axmp.epct, located at e.g.
/home/dicostest/tosFiles/to14/ad13.1/
               Back to Contents

axmp.epct should not be used for to14, since it does not have any AXmp HW.

Example of file contents:

SOFTWARE
	IDP/D8;		// AxmpSupervision_IDP, Optional

ENVIRONMENT DATA

AXMP_POLL_INTERVAL = "20000"
AXMP_ADDRESSES = "to14s7c1:9977,to14s7c2:9977"
AXMP_HIGH_TEMP = "50"
AXMP_VOLTAGE_INTERVAL = "24-33"

ENDDATA

File servicePlatform.epct with the applications AC, HLR and SCP, located at e.g.
/home/dicostest/tosFiles/to14/ad13.1/
               Back to Contents

Example of file contents:
SOFTWARE
	IDG/SERVICEPLATFORM,
	IDG/HLR,
	IDG/AC,
	IDP/POPULATOR,
	IDG/SCP;

// ALLOCATE DfsCosNamingResponder_DUT TO DbaPool;	
INITIAL DATA

# The following are our two SS7 Machines
# Both rev A and rev B+ for the HLR application are required below
The_IP_Address = "134.138.57.40"
The_IP_Address_Dual = "134.138.58.40"
Count_IP_Port = 4
The_IP_Port = 8001		# Old HLR (SSN5), HLR protocol rev A
The_IP_Port2 = 8002		# New HLR (SSN6), HLR protocol rev B+
The_IP_Port3 = 8003		# AC (SSN10)
The_IP_Port4 = 8004		# SCP (SSN55)

The_Second_IP_Address = "134.138.57.41"
The_Second_IP_Address_Dual = "134.138.58.41"
Count_Second_IP_Port = 4
The_Second_IP_Port = 8001	# Old HLR (SSN5), HLR protocol rev A
The_Second_IP_Port2 = 8002	# New HLR (SSN6), HLR protocol rev B+
The_Second_IP_Port3 = 8003	# AC (SSN10)
The_Second_IP_Port4 = 8004	# SCP (SSN55)

Count_SS7_Activated = 2 

MonitorTableSize = 16384
SignallerTableSize = 2048
MaxPortNamePublications = 4000
Ddb_majorTrace = (245)

ENDDATA

File pools.epct with the applications AC, HLR and SCP, located at e.g.
/home/dicostest/tosFiles/to14/ad13.1/
               Back to Contents

Example of file contents:
PROCESSOR Processor1 ALSO IN DbaPool,PopExePool;
PROCESSOR Processor2 ALSO IN DbaPool,PopExePool;
PROCESSOR Processor3 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor4 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor5 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor6 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor7 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor8 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor9 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor10 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor11 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor12 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor13 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor14 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor15 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor16 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor17 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor18 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor19 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor20 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor21 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor22 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor23 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor24 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor25 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor26 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor27 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;

File Jambala.epct               Back to Contents

Example of file contents:
// Jambala.epct
// ------------

//  Revision History
//  ----------------
//  1999-09-30  lmcbetr		Rename from ServicePlatform.epct to Jambala.epct
//					Put all software in Jambala.epct and all INITIAL DATA in 
//					JambalaData.epct


////// Configuration Name
// build the name of the configuration using version of applications.
// use the name generated by the build process (see http://panam.lmc.ericsson.se/tcm_k/cgi/convention.txt)
// but replace '.' by '_'

NAME JAM_PL_1_1_12_SCP_2_0_5;

////// Zone
// For network redundancy to find out what network the system belongs to.
// ZONE 1 is default if not typed, the redundant network should be named
// ZONE 2.

ZONE 1;


////// Software 
// list all IDG, IDP or LM required for the configuration
// don't forget the semi-colon (;) at the end

SOFTWARE
   //TelOrb software
       IDP/MD14    // Dicos_IDP 
      ,IDP/MD16    // Ethernet Loading and Communication
      ,IDP/DUO2    // Net_IDP, to show load on processors 
//      ,IDP/D2      // NetRed_IDP, (optional)
//      ,IDP/D3      // Hardware Alarm collector (optional)
//      ,IDP/MD17    // LoadLinkUdpAdaptation_IDP (optional)
      ,IDP/MD18    // Java VM, (optional, required for the Scp)

  // Jambala Software
      ,IDG/SERVICEPLATFORM         // base for all applications
      ,IDG/HLR
      ,IDG/AC
      ,IDG/SCP
	;

File JambalaData.epct               Back to Contents

Example of file contents:
// JambalaData.epct 
// ----------------
//  
//  Revision History
//  ----------------
//  1999-09-30  lmcbetr		Rename from TelOrb.epct to JambalaData.epct
//                            Add documentation on a few tags after uablrek comments
//					Increase SignallerTableSize to 3000
//					Increase TimeoutTableSize to 32767
//					Put all software in Jambala.epct and all INITIAL DATA in 
//					JambalaData.epct
//
//  1999-09-29  lmcbetr		Complete revision, merge of Ethernet.epct, Net.epct, Data.epct
//					TelOrb.epct, UdpLoading.epct, NTP.epct
//


INITIAL DATA
#### Comments in initial data section must start with '#'

### SHELL ports
# port address base for the telnet shell
# add the index of the processor you are trying to connect to
# e.g. 8014 for processor 5
ShellTelnetPortNoBase = 8010

# port address base for the http connection
# add the index of the processor you are trying to connect to
# e.g. 5614 for processor 5
ShellHttpPortNoBase = 5610

### Q-Util
# port address for the Q-Util shell
KernelUtilityDaemonPort = 42015   


### ORB
# Host address of IIOP gateway
# normally it is the names of the first two processors
DorbIIOPHostName = "TelorbProc1:TelorbProc2"
DorbIIOPPort = 56001

# When 1 telorb prints the IOR on the console
IOR_PRINT = 1

# tracing (0 = OFF, 1 = ON)
IIOP_GatewayVerbose = 0


### DBN record table size
# Max objects/processor including replication
# Example: 1000000 subscribers each consisting of 10 POT (objects) with 
# replicas and a margin for backup and reconfiguration.
# (1000000 * 10 * 2 * 2) / (28 - 1) rounded is 1500000 and then an 
# 10% margin extra gives 1650000
# Explanations
# (maximum number of subscribers when the system is fully configured for 
# this number of processors) * (POT (objects) per subscriber) * 
# (doubling for replicas) * (doubling for backup) / (number of processors) - 
# (compensate that one processor can be out of service, that gives the 
# margin for reconfiguration(if the loaders are not used for normal
# traffic they should be withdrawn as well)) 
# Check memory cost afterwards, it is 16B x DdbRecordTabMasterSize
# DB table sizes
### For Ac, we have only one POT (AuthData)
### For Hlr, we estimate to 7 (HlrSubscriber, StoredLocation + 5 services)
### for Platform, we have 3 POTs (Min, Dirnum, basicSubscriber) POTs per subscriber
### For Scp, we estimate to 7 POTS (ScpSubscriber (individual or group) + 6 POTs for services,
###         (some Scp services needs more than one pot )
### for Argentina, we supposed 200000 Scp subscribers, over 5 traffic processors
DdbRecordTabMasterSize = 2200000


### MDP
# How many Mdp objects (DU:s with POT:s) that can be in the table,
# rounded upwards
# ((HlrSubscriber+ScpSubscriber+ScpGroup+AcSubscriber+BasicSubscriber+Min+Dirnum+Esn) * 911) = 7300
#  + All other keyed POTs (1 DU per DUT)
# ?maybe 8000 is enough?
#  [is there any Mdp in Telorb that we have to count?]
DdbMdpTabSize = 10000


### Garbage Collecting for Lazy copy of data.
# This is the interval in which the DBMS lazy record table is
# iterated through  to remove copies from a processor.
# UAB Recommended value is 60 seconds.
DdbLazyPurgeInterval = 60000           

# Lazy copy table size (uab recommended value = 100000)
DdbRecordTabLazySize = 100000

### BACKUP
# uncompressed LM size for target systems 4MByte or 0x3D0900
# (size for Vega simulated systems 1MByte or 0xF4240)
DdbBackupLoadmoduleSectionSize = 0x3D0900 

#### dump tool configuration and usage
#
# The `dumpd' tool should be used to retrieve dumps on a
# Unix host. Type `dumpd -h' to get help for `dumpd'.
# The dump files are ASCII-text (for now) and are stored in the
# directory where `dumpd' is started. The filenames are
#
#       DicosTextDump-n                 For Capsule dumps
#       DicosProcessorTextDump-n        For Processor dumps
#
# Where `n' is an index.
# The dump files are analyzed with the `epelfaddr_dmp' script.
 
# DUMP_MODE: bit 0 -    Console dump
#            bit 1 -    Remote Capsule Dump
#            bit 2 -    Remote Processor Dump
# '1' means "ON", to turn everything on set DUMP_MODE = 7
DUMP_MODE = 7
 
# DUMP_HOST_ID: The IP-address of the host where `dumpd' is running
#DUMP_HOST_ID = (134,138,25,107) # this is used instead in the bootptab,T151 
 
# The UDP-port that `dumpd' listens on.
# The default port for `dumpd' is 5556.
DUMP_HOST_PORT = 5556
 
# DUMP_GATEWAY_1
# DUMP_GATEWAY_2 : IP-gateways to the `DUMP_HOST_ID'
# (these should be omitted if gateways are not needed)
#DUMP_GATEWAY_1 = (134,138,18,1)
#DUMP_GATEWAY_2 = (134,138,17,1)
 
# DUMP_DRIVER: The name of the driver for remote dumps,
# should always be "DumpDriverTftp" for now.
DUMP_DRIVER = "DumpDriverTftp"
#
# End of dump tool stuff


### Time service 
# The IP and port of the NTP server (port = 123 is default) 
# NTP_SERVER_IP = (134,138,25,107) # this is used instead in the bootptab 
NTP_SERVER_PORT = 5566

# TIME_TZ_OFFSET is the Local Time Zone offset in hours.
# Because only positive numbers can be given here the number is adjusted:
# intOffset = (TIME_TZ_OFFSET > 12) ? TIME_TZ_OFFSET-24 : TIME_TZ_OFFSET;
TIME_TZ_OFFSET = 19

### INITIAL DATA for the optional Java IDP, if used remove the comments
# Java Virtual Machine (JVM)
# To avoid lack of memory in the JVM, perform the following settings.
# The sizes are in Mega-byte. Default values are 4Mbyte for the JVM, and
# 8Mbyte for the entire JVM-Capsule.
# JAVA_HEAP - Is the size available for Java-code and Java-data.
#             The size must be big enough to hold all your (un-packed)
#             application classes, and all data (objects).
#             Maximum value seems to be 27Mbyte.
# JAVA_CAPSULE_HEAP - Is OPTIONAL. If not specified it is set to
#             JAVA_HEAP+4Mbyte. The size must be big enough to hold the
#             entire JAVA_HEAP, plus the JVM-code and internal data,
#             AND all JavaJar-LMs that you load initially.
#             Maximum value seems to be 31Mbyte.
# UAB Recommendation : always use the maximum values for the SCP
# The JavaJar-LMs are temporary stored on the Capsule-heap until the JVM
# is completely started.
#JAVA_HEAP = 4  # default value, see explanation above for your own value
JAVA_HEAP = 22
JAVA_CAPSULE_HEAP = 31


### INITIAL DATA for the optional Hardware Alarms Collector
# (KnuerrRms_IDP). If used remove the comments.
# Knuerr HW alarm
# The IP address for the Hardware Alarms Collector (Knuerr RMS)
# Replace this IP address with your local IP address
RMS_IP_ADDRESS = "134.138.187.101"

## RMS_NO_CABINET_B = 0, the system consist of two cabinets
## RMS_NO_CABINET_B = 1, the system consist of one cabinet
RMS_NO_CABINET_B = 1
## magic numbers...
RMS_MAX_TEMP = 60
RMS_POLL_INTERVAL = 15000


### IPC parameters
# Level where messages to not connected ports do not get through
IpcOverloadRejectLevels = (100, 200, 50000)
# Level where overload warning is sent for connected ports
IpcOverloadWarningLevels = (100, 200, 50000)
# Level where messages are aborted for connected ports
IpcOverloadAbortLevels = (400,800, 100000)


#### NETWORK REDUNDANCY
# These values are magic numbers provided by UAB to LMC
DdbExtSynchNoOfProcesses = 5
DdbnrProcBacklogBytes = 90000000
DdbnrNoOfPseudoParticipants = 30


### MonitorTableSize 
# Default = 2047 (way too low!!)
# The maximum number of simultaneous monitors on a processor.
# Monitors are mainly used by the JVM .
# UAB recommandation: 16384 seems reasonable, maybe a little low.
MonitorTableSize = 16384


### SignallerTableSize 
# Default = "NotificationTableSize" = 256 (way too low!!)
# The maximum number of simultaneous signallers on a processor.
# Signallers are used for entering a job in the job-queue to a thread.
# They are used to wake up the "Process Threads" in Java, and for resuming
# execution on a synchronous file-system access (among other things).
# You will need at least one per simultaneous Java process, and one per
# outstanding file-system operation.
# UAB recommandation: 2048 seems a little low.
SignallerTableSize = 3000


### MaxPortNamePublications 
# Default = 2000
# The maximum number of named ports in the system (not processor this time).
# Named ports are used for server processes. Each process type (not process
# instance) publishes a port per processor it is allocated to.
# UAB recommandation: 4000 seems Ok.
MaxPortNamePublications = 4000


### TimeoutTableSize 
# Default =  2047 (way too low!!)
# The maximum number of simultaneously running timers. This is
# impossible to estimate. Timers are used everywhere.
# I think the memory usage is only 1 pointer (4 byte) per entry in
# the table so I think you can increase the value without running out of
# memory.
# UAB recommandation: --- 16383 I would double it just to be sure :-)
TimeoutTableSize = 32767

### ScpProcess INITIAL DATA
# this identifies the ScpProcess process to be used by the distributor
# valid values are
# "ScpProcess" : (default) java process
# "ScpTrafficFramework" : C++ process
ScpFactory_processName = "ScpProcess"
        
#### Distributor INITIAL DATA
# Connection to the SS7 stacks and the wrapper
# Provide 2 ip addresses per stack
# and the ip port to connect to
# must match with the wrapper configuration
# There should be one port per SSN.

# number of stacks
Count_SS7_Activated = 2

# first stack
The_IP_Address = "172.16.1.151"
The_IP_Address_Dual = "172.17.1.151"
Count_IP_Port        = 6
The_IP_Port = 8001
The_IP_Port2 = 8002
The_IP_Port3 = 8003
The_IP_Port4 = 8004
The_IP_Port5 = 8005
The_IP_Port6 = 8006

# second stack
The_Second_IP_Address = "172.16.1.152"
The_Second_IP_Address_Dual = "172.17.1.152"
Count_Second_IP_Port = 6
The_Second_IP_Port = 8001
The_Second_IP_Port2 = 8002
The_Second_IP_Port3 = 8003
The_Second_IP_Port4 = 8004
The_Second_IP_Port5 = 8005
The_Second_IP_Port6 = 8006


###  OLD TAGS REMOVED  
#
# NTP_POLL_INTERVAL shall not be used anymore.
#
# The TIME_DST_DATES just specifies a default on initial start.
# The best on a real system is probably to omit this totally, and
# enter the DST-dates via the CORBA interface when the system is
# started, and then take a backup (the DSTs are stored in the database).
#
# IpcPortTableSize does not have to be specified, the default value 
# (32767) is ok.
# 
# Trace tags shall be removed.
# (DEBUG_MODE, DbdPOTLoadTrace, Ddb_majorTrace, HEAP_DEBUG, Ddb_vitalTrace, ...)
# 


ENDDATA

File Processor.epct               Back to Contents

Example of file contents:
// Processor.epct
// --------------
//
//	Revision History
//	----------------
//
//    1999-09-30  lmcbetr       Cleanup, add redundancy pools.


/// Set ethernet address according to the hardware configuration of the system.
/// And create enough processor for the actual system
PROCESSOR Processor1
     INITIAL
     TARGET i486 
     TYPE DcpsimEmMo
     LOADER
     ADDRESS "00:80:50:00:cb:0b 00:80:50:00:8f:f9"
     IN DicosCommonPool, DicosPlgLoaderPool, DicosDbReplicaPool, DicosQnPool;
PROCESSOR Processor2
     TARGET i486 
     TYPE DcpsimEmMo
     LOADER
     ADDRESS "00:80:50:00:cb:00 00:80:50:00:8f:de"
     IN DicosCommonPool, DicosPlgLoaderPool, DicosDbReplicaPool, DicosQnPool;
PROCESSOR Processor3
     TARGET i486 
     TYPE DcpsimEmMo
     ADDRESS "00:80:50:00:cb:21 00:80:50:00:8e:f5" 
     IN DicosCommonPool;
PROCESSOR Processor4
     TARGET i486 
     TYPE DcpsimEmMo
     ADDRESS "00:80:50:00:ca:ff 00:80:50:00:8e:e1" 
     IN DicosCommonPool;
PROCESSOR Processor5
     TARGET i486 
     TYPE DcpsimEmMo
     ADDRESS "00:80:50:00:c9:82 00:80:50:00:8a:55"
     IN DicosCommonPool;
PROCESSOR Processor6
     TARGET i486 
     TYPE DcpsimEmMo
     ADDRESS "00:80:50:00:cb:03 00:80:50:00:8e:c5" 
     IN DicosCommonPool;
PROCESSOR Processor7
     TARGET i486
     TYPE DcpsimEmMo
     ADDRESS "00:80:50:00:ca:f9 00:80:50:00:8e:d9"
     IN DicosCommonPool;



/// Other TelOrb Pools
/// If an application or function is not installed,
/// just comment out the corresponding pool.
///
/// NetworkRedundancy  (IDP/D2)
/// -----------------

PROCESSOR Processor1 ALSO IN DicosNetRedPool, DicosNetRedConnectPool;
PROCESSOR Processor2 ALSO IN DicosNetRedPool, DicosNetRedConnectPool;
PROCESSOR Processor3 ALSO IN DicosNetRedPool;
PROCESSOR Processor4 ALSO IN DicosNetRedPool;
PROCESSOR Processor5 ALSO IN DicosNetRedPool;
PROCESSOR Processor6 ALSO IN DicosNetRedPool;
PROCESSOR Processor7 ALSO IN DicosNetRedPool;


/// Jambala pools
///
/// DbaPool  (IDG/SERVICEPLATFORM)
/// -------

PROCESSOR Processor1 ALSO IN DbaPool;
PROCESSOR Processor2 ALSO IN DbaPool;

/// DistributorPool (IDG/SERVICEPLATFORM)
/// ---------------

PROCESSOR Processor3 ALSO IN DistributorPool;
PROCESSOR Processor4 ALSO IN DistributorPool;
PROCESSOR Processor5 ALSO IN DistributorPool;
PROCESSOR Processor6 ALSO IN DistributorPool;
PROCESSOR Processor7 ALSO IN DistributorPool;


/// AcPool (IDG/AC)
/// ------

PROCESSOR Processor3 ALSO IN AcPool;
PROCESSOR Processor4 ALSO IN AcPool;
PROCESSOR Processor5 ALSO IN AcPool;
PROCESSOR Processor6 ALSO IN AcPool;
PROCESSOR Processor7 ALSO IN AcPool;

/// HlrPool (IDG/HLR)
/// -------

PROCESSOR Processor3 ALSO IN HlrPool;
PROCESSOR Processor4 ALSO IN HlrPool;
PROCESSOR Processor5 ALSO IN HlrPool;
PROCESSOR Processor6 ALSO IN HlrPool;
PROCESSOR Processor7 ALSO IN HlrPool;


/// ScpPool (IDG/SCP)
/// -------

PROCESSOR Processor3 ALSO IN ScpPool;
PROCESSOR Processor4 ALSO IN ScpPool;
PROCESSOR Processor5 ALSO IN ScpPool;
PROCESSOR Processor6 ALSO IN ScpPool;
PROCESSOR Processor7 ALSO IN ScpPool;

File S34Dhcp_isc on IO processors 1 and 2, located at /etc/rc3.d/               Back to Contents

Example of file contents:
#!/bin/sh
#
#set -x

if [ ! -d /usr/sbin ]
then                    # /usr not mounted
        exit
fi

killproc()
 {              # kill the named process(es)
    # if there are more services that need to be stopped, add a string
    # given by 'ps -e' to the list
    servicesToBeStopped=$1

    # find out which pids shall be killed
    pid=`/bin/ps -e | /bin/egrep ${servicesToBeStopped} | /bin/awk '{print $1}'`
    # save the name of all processes to be stopped
    name=`/bin/ps -e | /bin/egrep ${servicesToBeStopped} | /bin/awk '{print $4}'`

    if [ -n "$pid" ]
    then
      /bin/kill $pid
      return 0
    fi
    return 1
}


case "$1" in
'start')
        # Only start if there is a config file
     if [ -f /opt/telorb/etc/start_dhcp ] ; then
             /opt/telorb/etc/start_dhcp
     fi
        ;;

'stop')
        killproc Dhcp.io
        killproc Dhcp.LM && echo "Dhcp stopped"
        ;;
'restart')

        killproc Dhcp.io
        killproc Dhcp.LM && echo "Dhcp stopped"

        # Only start if there is a config file
     if [ -f /opt/telorb/etc/start_dhcp ] ; then
             /opt/telorb/etc/start_dhcp
     fi
        ;;
*)
        echo "Usage: /etc/rc3.d/S34Dhcp_isc { start | stop | restart }"
        ;;
esac
exit 0


File start_dhcp on IO processors 1 and 2, located at /opt/telorb/etc/               Back to Contents

Example of file contents:
#!/bin/csh
source /opt/telorb/codearchive/Unix_IDP/env/setup.csh

## Start the dhcp
/opt/telorb/codearchive/Unix_IDP/Dhcp_LM/scripts/Dhcp.io.csh /opt/telorb/etc/dhcpd.pxe.conf -lf /opt/telorb/etc/dhcpd.leases -cf /opt/telorb/etc/dhcpd.pxe.conf exp0 exp1&


File dhcpd.pxe.conf on IO processor 1 without terminal server, located at /opt/telorb/etc/               Back to Contents

Example of file contents:
# this is the dhcpd configuration file used by
# the ISC version 3 dhcpd.

option time-offset 3600;

# Ip address of timeservers 
option time-servers 134.138.58.26, 134.138.57.25;

# define site specific options
option epTftpdServerAddress    code 152 = ip-address;
option dumpServerAddress       code 153 = array of ip-address;
option consoleServerAddress    code 154 = array of ip-address;
option consoleServerPort       code 155 = unsigned integer 16;

# define the dicos processors
# wrap all the dicos processors into one shared network in order to
# get dhcpd to answer bootp requests regarding interfaces on other
# networks.

shared-network dicosProcessor {
   subnet 134.138.57.0 netmask 255.255.255.0 {
      option routers 134.138.57.1;
      option subnet-mask 255.255.255.0;
      option broadcast-address 134.138.57.255;
      next-server 134.138.57.25;
   }
   subnet 134.138.58.0 netmask 255.255.255.0 {
      option routers 134.138.58.1;
      option subnet-mask 255.255.255.0;
      option broadcast-address 134.138.58.255;
      next-server 134.138.58.25;
   }
   option dumpServerAddress    134.138.58.26, 134.138.57.25;
   option consoleServerAddress 134.138.57.25;
   option consoleServerPort    7000;

filename "telorb/ppro/plLoadable";
}

# define the processors
host p1_0 {
   hardware ethernet 00:30:f7:00:c1:bd;
   fixed-address     134.138.57.101;
# this processor is a loader
   option epTftpdServerAddress 134.138.57.25;
}

host p1_1 {
   hardware ethernet 00:a0:a5:12:13:88;
   fixed-address     134.138.58.101;
# this processor is a loader
   option epTftpdServerAddress 134.138.58.25;
}

host p2_0 {
   hardware ethernet 00:30:f7:00:c7:65;
   fixed-address     134.138.57.102;
# this processor is a loader
   option epTftpdServerAddress 134.138.57.25;
}

host p2_1 {
   hardware ethernet 00:a0:a5:12:11:34;
   fixed-address     134.138.58.102;
# this processor is a loader
   option epTftpdServerAddress 134.138.58.25;
}

host p3_0 {
   hardware ethernet 00:30:f7:00:c7:8f;
   fixed-address     134.138.57.103;
}

host p3_1 {
   hardware ethernet 00:a0:a5:12:17:d3;
   fixed-address     134.138.58.103;
}

host p4_0 {
   hardware ethernet 00:30:f7:00:c1:e9;
   fixed-address     134.138.57.104;
}

host p4_1 {
   hardware ethernet 00:a0:a5:12:11:35;
   fixed-address     134.138.58.104;
}

host p5_0 {
   hardware ethernet 00:30:f7:00:c1:dc;
   fixed-address     134.138.57.105;
}

host p5_1 {
   hardware ethernet 00:a0:a5:12:11:4a;
   fixed-address     134.138.58.105;
}

host p6_0 {
   hardware ethernet 00:30:f7:00:c7:69;
   fixed-address     134.138.57.106;
}

host p6_1 {
   hardware ethernet 00:a0:a5:12:11:15;
   fixed-address     134.138.58.106;
}

host p7_0 {
   hardware ethernet 00:30:f7:00:c5:89;
   fixed-address     134.138.57.107;
}

host p7_1 {
   hardware ethernet 00:a0:a5:12:13:90;
   fixed-address     134.138.58.107;
}

host p8_0 {
   hardware ethernet 00:30:f7:00:c7:b0;
   fixed-address     134.138.57.108;
}

host p8_1 {
   hardware ethernet 00:a0:a5:12:18:51;
   fixed-address     134.138.58.108;
}

host p9_0 {
   hardware ethernet 00:30:f7:00:c1:fc;
   fixed-address     134.138.57.109;
}

host p9_1 {
   hardware ethernet 00:a0:a5:12:13:7c;
   fixed-address     134.138.58.109;
}

host p10_0 {
   hardware ethernet 00:30:f7:00:c2:28;
   fixed-address     134.138.57.110;
}

host p10_1 {
   hardware ethernet 00:a0:a5:12:11:4c;
   fixed-address     134.138.58.110;
}

host p11_0 {
   hardware ethernet 00:30:f7:00:c1:c8;
   fixed-address     134.138.57.111;
}

host p11_1 {
   hardware ethernet 00:a0:a5:12:13:a6;
   fixed-address     134.138.58.111;
}

host p12_0 {
   hardware ethernet 00:30:f7:00:c2:1f;
   fixed-address     134.138.57.112;
}

host p12_1 {
   hardware ethernet 00:a0:a5:12:0f:4e;
   fixed-address     134.138.58.112;
}

host p13_0 {
   hardware ethernet 00:30:f7:00:c1:bc;
   fixed-address     134.138.57.113;
}

host p13_1 {
   hardware ethernet 00:a0:a5:12:13:a7;
   fixed-address     134.138.58.113;
}

host p14_0 {
   hardware ethernet 00:30:f7:00:c1:b3;
   fixed-address     134.138.57.114;
}

host p14_1 {
   hardware ethernet 00:a0:a5:12:14:4e;
   fixed-address     134.138.58.114;
}

host p15_0 {
   hardware ethernet 00:30:f7:00:c2:17;
   fixed-address     134.138.57.115;
}

host p15_1 {
   hardware ethernet 00:a0:a5:12:13:9c;
   fixed-address     134.138.58.115;
}

host p16_0 {
   hardware ethernet 00:30:f7:00:c1:d7;
   fixed-address     134.138.57.116;
}

host p16_1 {
   hardware ethernet 00:a0:a5:12:14:16;
   fixed-address     134.138.58.116;
}

host p17_0 {
   hardware ethernet 00:30:f7:00:c7:7d;
   fixed-address     134.138.57.117;
}

host p17_1 {
   hardware ethernet 00:a0:a5:12:18:4a;
   fixed-address     134.138.58.117;
}

host p18_0 {
   hardware ethernet 00:30:f7:00:c2:1b;
   fixed-address     134.138.57.118;
}

host p18_1 {
   hardware ethernet 00:a0:a5:12:13:a3;
   fixed-address     134.138.58.118;
}

host p19_0 {
   hardware ethernet 00:30:f7:00:c2:00;
   fixed-address     134.138.57.119;
}

host p19_1 {
   hardware ethernet 00:a0:a5:12:13:96;
   fixed-address     134.138.58.119;
}

host p20_0 {
   hardware ethernet 00:30:f7:00:c1:da;
   fixed-address     134.138.57.120;
}

host p20_1 {
   hardware ethernet 00:a0:a5:12:13:93;
   fixed-address     134.138.58.120;
}

host p21_0 {
   hardware ethernet 00:30:f7:00:c2:0d;
   fixed-address     134.138.57.121;
}

host p21_1 {
   hardware ethernet 00:a0:a5:12:13:a5;
   fixed-address     134.138.58.121;
}

host p22_0 {
   hardware ethernet 00:30:f7:00:c1:a6;
   fixed-address     134.138.57.122;
}

host p22_1 {
   hardware ethernet 00:a0:a5:12:13:92;
   fixed-address     134.138.58.122;
}

host p23_0 {
   hardware ethernet 00:30:f7:00:c1:b1;
   fixed-address     134.138.57.123;
}

host p23_1 {
   hardware ethernet 00:a0:a5:12:11:69;
   fixed-address     134.138.58.123;
}

host p24_0 {
   hardware ethernet 00:30:f7:00:c1:a2;
   fixed-address     134.138.57.124;
}

host p24_1 {
   hardware ethernet 00:a0:a5:12:13:94;
   fixed-address     134.138.58.124;
}

host p25_0 {
   hardware ethernet 00:30:f7:00:c1:b0;
   fixed-address     134.138.57.125;
}

host p25_1 {
   hardware ethernet 00:a0:a5:12:14:17;
   fixed-address     134.138.58.125;
}

host p26_0 {
   hardware ethernet 00:30:f7:00:c1:db;
   fixed-address     134.138.57.126;
}

host p26_1 {
   hardware ethernet 00:a0:a5:12:13:c1;
   fixed-address     134.138.58.126;
}

host p27_0 {
   hardware ethernet 00:30:f7:00:d6:88;
   fixed-address     134.138.57.127;
}

host p27_1 {
   hardware ethernet 00:a0:a5:12:13:a2;
   fixed-address     134.138.58.127;
}

host p28_0 {
   hardware ethernet 00:30:f7:00:d6:8b;
   fixed-address     134.138.57.128;
}

host p28_1 {
   hardware ethernet 00:a0:a5:12:13:86;
   fixed-address     134.138.58.128;
}

Comments:

File dhcpd.pxe.conf on IO processor 2 without terminal server, located at /opt/telorb/etc/               Back to Contents

Example of file contents:
# this is the dhcpd configuration file used by
# the ISC version 3 dhcpd.

option time-offset 3600;

# Ip address of timeservers 
option time-servers 134.138.58.26, 134.138.57.25;

# define site specific options
option epTftpdServerAddress    code 152 = ip-address;
option dumpServerAddress       code 153 = array of ip-address;
option consoleServerAddress    code 154 = array of ip-address;
option consoleServerPort       code 155 = unsigned integer 16;

# define the dicos processors
# wrap all the dicos processors into one shared network in order to
# get dhcpd to answer bootp requests regarding interfaces on other
# networks.

shared-network dicosProcessor {
   subnet 134.138.57.0 netmask 255.255.255.0 {
      option routers 134.138.57.1;
      option subnet-mask 255.255.255.0;
      option broadcast-address 134.138.57.255;
      next-server 134.138.57.26;
   }
   subnet 134.138.58.0 netmask 255.255.255.0 {
      option routers 134.138.58.1;
      option subnet-mask 255.255.255.0;
      option broadcast-address 134.138.58.255;
      next-server 134.138.58.26;
   }
   option dumpServerAddress    134.138.58.26, 134.138.57.25;
   option consoleServerAddress 134.138.57.25;
   option consoleServerPort    7000;

filename "telorb/ppro/plLoadable";
}

# define the processors
host p1_0 {
   hardware ethernet 00:30:f7:00:c1:bd;
   fixed-address     134.138.57.101;
# this processor is a loader
   option epTftpdServerAddress 134.138.57.26;
}

host p1_1 {
   hardware ethernet 00:a0:a5:12:13:88;
   fixed-address     134.138.58.101;
# this processor is a loader
   option epTftpdServerAddress 134.138.58.26;
}

host p2_0 {
   hardware ethernet 00:30:f7:00:c7:65;
   fixed-address     134.138.57.102;
# this processor is a loader
   option epTftpdServerAddress 134.138.57.26;
}

host p2_1 {
   hardware ethernet 00:a0:a5:12:11:34;
   fixed-address     134.138.58.102;
# this processor is a loader
   option epTftpdServerAddress 134.138.58.26;
}

host p3_0 {
   hardware ethernet 00:30:f7:00:c7:8f;
   fixed-address     134.138.57.103;
}

host p3_1 {
   hardware ethernet 00:a0:a5:12:17:d3;
   fixed-address     134.138.58.103;
}

host p4_0 {
   hardware ethernet 00:30:f7:00:c1:e9;
   fixed-address     134.138.57.104;
}

host p4_1 {
   hardware ethernet 00:a0:a5:12:11:35;
   fixed-address     134.138.58.104;
}

host p5_0 {
   hardware ethernet 00:30:f7:00:c1:dc;
   fixed-address     134.138.57.105;
}

host p5_1 {
   hardware ethernet 00:a0:a5:12:11:4a;
   fixed-address     134.138.58.105;
}

host p6_0 {
   hardware ethernet 00:30:f7:00:c7:69;
   fixed-address     134.138.57.106;
}

host p6_1 {
   hardware ethernet 00:a0:a5:12:11:15;
   fixed-address     134.138.58.106;
}

host p7_0 {
   hardware ethernet 00:30:f7:00:c5:89;
   fixed-address     134.138.57.107;
}

host p7_1 {
   hardware ethernet 00:a0:a5:12:13:90;
   fixed-address     134.138.58.107;
}

host p8_0 {
   hardware ethernet 00:30:f7:00:c7:b0;
   fixed-address     134.138.57.108;
}

host p8_1 {
   hardware ethernet 00:a0:a5:12:18:51;
   fixed-address     134.138.58.108;
}

host p9_0 {
   hardware ethernet 00:30:f7:00:c1:fc;
   fixed-address     134.138.57.109;
}

host p9_1 {
   hardware ethernet 00:a0:a5:12:13:7c;
   fixed-address     134.138.58.109;
}

host p10_0 {
   hardware ethernet 00:30:f7:00:c2:28;
   fixed-address     134.138.57.110;
}

host p10_1 {
   hardware ethernet 00:a0:a5:12:11:4c;
   fixed-address     134.138.58.110;
}

host p11_0 {
   hardware ethernet 00:30:f7:00:c1:c8;
   fixed-address     134.138.57.111;
}

host p11_1 {
   hardware ethernet 00:a0:a5:12:13:a6;
   fixed-address     134.138.58.111;
}

host p12_0 {
   hardware ethernet 00:30:f7:00:c2:1f;
   fixed-address     134.138.57.112;
}

host p12_1 {
   hardware ethernet 00:a0:a5:12:0f:4e;
   fixed-address     134.138.58.112;
}

host p13_0 {
   hardware ethernet 00:30:f7:00:c1:bc;
   fixed-address     134.138.57.113;
}

host p13_1 {
   hardware ethernet 00:a0:a5:12:13:a7;
   fixed-address     134.138.58.113;
}

host p14_0 {
   hardware ethernet 00:30:f7:00:c1:b3;
   fixed-address     134.138.57.114;
}

host p14_1 {
   hardware ethernet 00:a0:a5:12:14:4e;
   fixed-address     134.138.58.114;
}

host p15_0 {
   hardware ethernet 00:30:f7:00:c2:17;
   fixed-address     134.138.57.115;
}

host p15_1 {
   hardware ethernet 00:a0:a5:12:13:9c;
   fixed-address     134.138.58.115;
}

host p16_0 {
   hardware ethernet 00:30:f7:00:c1:d7;
   fixed-address     134.138.57.116;
}

host p16_1 {
   hardware ethernet 00:a0:a5:12:14:16;
   fixed-address     134.138.58.116;
}

host p17_0 {
   hardware ethernet 00:30:f7:00:c7:7d;
   fixed-address     134.138.57.117;
}

host p17_1 {
   hardware ethernet 00:a0:a5:12:18:4a;
   fixed-address     134.138.58.117;
}

host p18_0 {
   hardware ethernet 00:30:f7:00:c2:1b;
   fixed-address     134.138.57.118;
}

host p18_1 {
   hardware ethernet 00:a0:a5:12:13:a3;
   fixed-address     134.138.58.118;
}

host p19_0 {
   hardware ethernet 00:30:f7:00:c2:00;
   fixed-address     134.138.57.119;
}

host p19_1 {
   hardware ethernet 00:a0:a5:12:13:96;
   fixed-address     134.138.58.119;
}

host p20_0 {
   hardware ethernet 00:30:f7:00:c1:da;
   fixed-address     134.138.57.120;
}

host p20_1 {
   hardware ethernet 00:a0:a5:12:13:93;
   fixed-address     134.138.58.120;
}

host p21_0 {
   hardware ethernet 00:30:f7:00:c2:0d;
   fixed-address     134.138.57.121;
}

host p21_1 {
   hardware ethernet 00:a0:a5:12:13:a5;
   fixed-address     134.138.58.121;
}

host p22_0 {
   hardware ethernet 00:30:f7:00:c1:a6;
   fixed-address     134.138.57.122;
}

host p22_1 {
   hardware ethernet 00:a0:a5:12:13:92;
   fixed-address     134.138.58.122;
}

host p23_0 {
   hardware ethernet 00:30:f7:00:c1:b1;
   fixed-address     134.138.57.123;
}

host p23_1 {
   hardware ethernet 00:a0:a5:12:11:69;
   fixed-address     134.138.58.123;
}

host p24_0 {
   hardware ethernet 00:30:f7:00:c1:a2;
   fixed-address     134.138.57.124;
}

host p24_1 {
   hardware ethernet 00:a0:a5:12:13:94;
   fixed-address     134.138.58.124;
}

host p25_0 {
   hardware ethernet 00:30:f7:00:c1:b0;
   fixed-address     134.138.57.125;
}

host p25_1 {
   hardware ethernet 00:a0:a5:12:14:17;
   fixed-address     134.138.58.125;
}

host p26_0 {
   hardware ethernet 00:30:f7:00:c1:db;
   fixed-address     134.138.57.126;
}

host p26_1 {
   hardware ethernet 00:a0:a5:12:13:c1;
   fixed-address     134.138.58.126;
}

host p27_0 {
   hardware ethernet 00:30:f7:00:d6:88;
   fixed-address     134.138.57.127;
}

host p27_1 {
   hardware ethernet 00:a0:a5:12:13:a2;
   fixed-address     134.138.58.127;
}

host p28_0 {
   hardware ethernet 00:30:f7:00:d6:8b;
   fixed-address     134.138.57.128;
}

host p28_1 {
   hardware ethernet 00:a0:a5:12:13:86;
   fixed-address     134.138.58.128;
}

Comments:

File inetd.conf on IO processor 1 and 2, located at /etc/               Back to Contents

Example of file contents:
#
#ident  "@(#)inetd.conf 1.33    98/06/02 SMI"   /* SVr4.0 1.5   */
#
#
# Configuration file for inetd(1M).  See inetd.conf(4).
#
# To re-configure the running inetd process, edit this file, then
# send the inetd process a SIGHUP.
#
# Syntax for socket-based Internet services:
#        
#
# Syntax for TLI-based Internet services:
#
#   tli     
#
# Ftp and telnet are standard Internet services.
#
ftp     stream  tcp     nowait  root    /usr/sbin/in.ftpd       in.ftpd
telnet  stream  tcp     nowait  root    /usr/sbin/in.telnetd    in.telnetd
#
# Tnamed serves the obsolete IEN-116 name server protocol.
#
#name   dgram   udp     wait    root    /usr/sbin/in.tnamed     in.tnamed
#
# Shell, login, exec, comsat and talk are BSD protocols.
#
#shell  stream  tcp     nowait  root    /usr/sbin/in.rshd       in.rshd
#login  stream  tcp     nowait  root    /usr/sbin/in.rlogind    in.rlogind
#exec   stream  tcp     nowait  root    /usr/sbin/in.rexecd     in.rexecd
#comsat dgram   udp     wait    root    /usr/sbin/in.comsat     in.comsat
#talk   dgram   udp     wait    root    /usr/sbin/in.talkd      in.talkd
#
# Must run as root (to read /etc/shadow); "-n" turns off logging in utmp/wtmp.
#
#uucp   stream  tcp     nowait  root    /usr/sbin/in.uucpd      in.uucpd
#
# Tftp service is provided primarily for booting.  Most sites run this
# only on machines acting as "boot servers." 
#
tftp    dgram   udp     wait    root    /usr/sbin/in.tftpd      in.tftpd -s /tftpboot
#
# Finger, systat and netstat give out user information which may be
# valuable to potential "system crackers."  Many sites choose to disable 
# some or all of these services to improve security.
#
#finger stream  tcp     nowait  nobody  /usr/sbin/in.fingerd    in.fingerd
#systat stream  tcp     nowait  root    /usr/bin/ps             ps -ef
#netstat        stream  tcp     nowait  root    /usr/bin/netstat        netstat -f inet
#
# Time service is used for clock synchronization.
#
#time   stream  tcp     nowait  root    internal
#time   dgram   udp     wait    root    internal
# 
# Echo, discard, daytime, and chargen are used primarily for testing.
#
#echo   stream  tcp     nowait  root    internal
#echo   dgram   udp     wait    root    internal
#discard        stream  tcp     nowait  root    internal
#discard        dgram   udp     wait    root    internal
#daytime        stream  tcp     nowait  root    internal
#daytime        dgram   udp     wait    root    internal
#chargen        stream  tcp     nowait  root    internal
#chargen        dgram   udp     wait    root    internal
#
#
# RPC services syntax:
#  /  rpc/   \
#   
#
#  can be either "tli" or "stream" or "dgram".
# For "stream" and "dgram" assume that the endpoint is a socket descriptor.
#  can be either a nettype or a netid or a "*". The value is
# first treated as a nettype. If it is not a valid nettype then it is
# treated as a netid. The "*" is a short-hand way of saying all the
# transports supported by this system, ie. it equates to the "visible"
# nettype. The syntax for  is:
#       *||{[,]}
# For example: 
# dummy/1       tli     rpc/circuit_v,udp       wait    root    /tmp/test_svc   test_svc
#
# Solstice system and network administration class agent server
#100232/10      tli     rpc/udp wait root /usr/sbin/sadmind     sadmind
#
# Rquotad supports UFS disk quotas for NFS clients
#
#rquotad/1      tli     rpc/datagram_v  wait root /usr/lib/nfs/rquotad  rquotad
#
# The rusers service gives out user information.  Sites concerned
# with security may choose to disable it.
#
#rusersd/2-3    tli     rpc/datagram_v,circuit_v        wait root /usr/lib/netsvc/rusers/rpc.rusersd    rpc.rusersd
#
# The spray server is used primarily for testing.
#
#sprayd/1       tli     rpc/datagram_v  wait root /usr/lib/netsvc/spray/rpc.sprayd      rpc.sprayd
#
# The rwall server allows others to post messages to users on this machine.
#
#walld/1                tli     rpc/datagram_v  wait root /usr/lib/netsvc/rwall/rpc.rwalld      rpc.rwalld
#
# Rstatd is used by programs such as perfmeter.
#
rstatd/2-4      tli   rpc/datagram_v wait root /usr/lib/netsvc/rstat/rpc.rstatd rpc.rstatd
#
# The rexd server provides only minimal authentication and is often not run
#
#rexd/1          tli  rpc/tcp wait root /usr/sbin/rpc.rexd     rpc.rexd
#
# rpc.cmsd is a data base daemon which manages calendar data backed
# by files in /var/spool/calendar
#
#
# Sun ToolTalk Database Server
#
100083/1        tli     rpc/tcp wait root /usr/dt/bin/rpc.ttdbserverd rpc.ttdbserverd
#
# UFS-aware service daemon
#
#ufsd/1 tli     rpc/*   wait    root    /usr/lib/fs/ufs/ufsd    ufsd -p
#
# Sun KCMS Profile Server
#
100221/1        tli     rpc/tcp wait root /usr/openwin/bin/kcms_server  kcms_server
#
# Sun Font Server
#
fs              stream  tcp     wait nobody /usr/openwin/lib/fs.auto    fs
#
# CacheFS Daemon
#
100235/1 tli rpc/tcp wait root /usr/lib/fs/cachefs/cachefsd cachefsd
#
# Kerbd Daemon
#
kerbd/4         tli     rpc/ticlts      wait    root    /usr/sbin/kerbd  kerbd
#
# Print Protocol Adaptor - BSD listener
#
printer         stream  tcp     nowait  root    /usr/lib/print/in.lpd   in.lpd
#
# GSS Daemon
#
100234/1        tli     rpc/ticotsord   wait    root    /usr/lib/gss/gssd gssd 
dtspc stream tcp nowait root /usr/dt/bin/dtspcd /usr/dt/bin/dtspcd
100068/2-5 dgram rpc/udp wait root /usr/dt/bin/rpc.cmsd rpc.cmsd
300326/4        tli     rpc/tcp wait    root    /platform/SUNW,Ultra-Enterprise-10000/lib/dr_daemon     dr_daemon

Comments:

File hosts on IO processor 1, located at /etc/               Back to Contents

Example of file contents:
#
# Internet host table
#
127.0.0.1       localhost       
134.138.187.54  to14io1 loghost
134.138.57.25   to14io1i2
134.138.58.25   to14io1i3

134.138.187.55  to14io2
134.138.57.26   to14io2i2
134.138.58.26   to14io2i3
134.138.57.25      to14io1.i2
134.138.58.25      to14io1.fe1

Comments:

File hosts on IO processor 2, located at /etc/               Back to Contents

Example of file contents:
#
# Internet host table
#
127.0.0.1       localhost       
134.138.187.55  to14io2 loghost
134.138.57.26   to14io2i2
134.138.58.26   to14io2i3

134.138.187.54  to14io1
134.138.57.25   to14io1i2
134.138.58.25   to14io1i3

Comments:

File hostname.exp0 on IO processor 1, located at /etc/               Back to Contents

Example of file contents:
to14io1i2

File hostname.exp0 on IO processor 2, located at /etc/               Back to Contents

Example of file contents:
to14io2i2

File hostname.exp1 on IO processor 1, located at /etc/               Back to Contents

Example of file contents:
to14io1i3

File hostname.exp1 on IO processor 2, located at /etc/               Back to Contents

Example of file contents:
to14io2i3

File hostname.hme0 on IO processor 1, located at /etc/               Back to Contents

Example of file contents:
to14io1

File hostname.hme0 on IO processor 2, located at /etc/               Back to Contents

Example of file contents:
to14io2

File hostname.hme1 on IO processor 1, located at /etc/               Back to Contents

Example of file contents:

No example available.


Comments:

File hostname.hme1 on IO processor 2, located at /etc/               Back to Contents

Example of file contents:

No example available.


Comments:

File telorb.conf on IO processors 1 and 2, located at /opt/telorb/etc/               Back to Contents

Example of file contents:
###################################################################
# This configuration-file specifies all data used to run telorb-related
# services on IO-machines
###################################################################

###################################################################
# define all timeservers; there may be more than one timeserver
# example:timeserver 134.138.77.26
# If both IO-machines are timeserver you should adress one through the
# first network, and the other through the second network.
###################################################################
timeserver 134.138.57.25
timeserver 134.138.58.26

###################################################################
# define the internal subnet, i.e. IO-processors and all dicosprocessors
# usually there are two internal networks
# To find out which interfaces you have and which networks are assigned
# to them type: "ifconfig -a" on you IO-machines
# Running the command on one IO-machine can give you the following output:
#  to6io1:~>ifconfig -a
#  lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
#        inet 127.0.0.1 netmask ff000000 
#  exp0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
#        inet 134.138.77.25 netmask ffffff00 broadcast 134.138.77.255
#  exp1: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
#        inet 134.138.33.33 netmask fffff800 broadcast 134.138.39.255
#  hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
#        inet 134.138.187.29 netmask fffff800 broadcast 134.138.191.255
#  hme1: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
#        inet 134.138.76.25 netmask ffffff00 broadcast 134.138.76.255
#
# Running the same on the other IO-machine gives you enough information.
# In the following example we assume that the interface-names are the
# same on IO1 and IO2.
###################################################################
internal-network subnet0 134.138.57.0
internal-network netmask0 255.255.255.0
internal-network defaultgw0 134.138.57.1
internal-network bcast0 134.138.57.255
internal-network io1net0 134.138.57.25
internal-network io2net0 134.138.57.26
internal-network io1interfacename0 exp0
internal-network io2interfacename0 exp0

internal-network subnet1 134.138.58.0
internal-network netmask1 255.255.255.0
internal-network defaultgw1 134.138.58.1
internal-network bcast1 134.138.58.255
internal-network io1net1 134.138.58.25
internal-network io2net1 134.138.58.26
internal-network io1interfacename1 exp1
internal-network io2interfacename1 exp1

###################################################################
# define how to boot the dicosprocessors
# use SMALLPROM or PXE
###################################################################
booting SMALLPROM
#booting PXE

###################################################################
# define dump-server ip-address
# If both IO-machines are dump-server you should adress one through the
# first network, and the other through the second network.
###################################################################
dumpserverip 134.138.57.25
dumpserverip 134.138.58.26

###################################################################
# define console-server ip-address
###################################################################
consserverip 134.138.57.25

###################################################################
# define first port for terminal-server
# e.g. tsport 7001
###################################################################
tsport 7001

###################################################################
# define all dicosprocessors, i.e. define the mac-address,
# ip-address
#
# if the processor shall be a loader the ip-address for the tftp-server
# has to be added (dicosprocessor1_0 eptftp_server_net0)
###################################################################
dicosprocessor1_0 eth_addr_for_eth0 00:30:f7:00:c1:bd
dicosprocessor1_0 ip_addr_for_eth0 134.138.57.101
dicosprocessor1_0 eptftp_server_net0

dicosprocessor1_1 eth_addr_for_eth1 00:a0:a5:12:13:88
dicosprocessor1_1 ip_addr_for_eth1 134.138.58.101
dicosprocessor1_1 eptftp_server_net1

dicosprocessor2_0 eth_addr_for_eth0 00:30:f7:00:c7:65
dicosprocessor2_0 ip_addr_for_eth0 134.138.57.102
dicosprocessor2_0 eptftp_server_net0

dicosprocessor2_1 eth_addr_for_eth1 00:a0:a5:12:11:34
dicosprocessor2_1 ip_addr_for_eth1 134.138.58.102
dicosprocessor2_1 eptftp_server_net1

dicosprocessor3_0 eth_addr_for_eth0 00:30:f7:00:c7:8f
dicosprocessor3_0 ip_addr_for_eth0 134.138.57.103

dicosprocessor3_1 eth_addr_for_eth1 00:a0:a5:12:17:d3
dicosprocessor3_1 ip_addr_for_eth1 134.138.58.103

dicosprocessor4_0 eth_addr_for_eth0 00:30:f7:00:c1:e9
dicosprocessor4_0 ip_addr_for_eth0 134.138.57.104

dicosprocessor4_1 eth_addr_for_eth1 00:a0:a5:12:11:35
dicosprocessor4_1 ip_addr_for_eth1 134.138.58.104

dicosprocessor5_0 eth_addr_for_eth0 00:30:f7:00:c1:dc
dicosprocessor5_0 ip_addr_for_eth0 134.138.57.105

dicosprocessor5_1 eth_addr_for_eth1 00:a0:a5:12:11:4a
dicosprocessor5_1 ip_addr_for_eth1 134.138.58.105

dicosprocessor6_0 eth_addr_for_eth0 00:30:f7:00:c7:69
dicosprocessor6_0 ip_addr_for_eth0 134.138.57.106

dicosprocessor6_1 eth_addr_for_eth1 00:a0:a5:12:11:15
dicosprocessor6_1 ip_addr_for_eth1 134.138.58.106

dicosprocessor7_0 eth_addr_for_eth0 00:30:f7:00:c5:89
dicosprocessor7_0 ip_addr_for_eth0 134.138.57.107

dicosprocessor7_1 eth_addr_for_eth1 00:a0:a5:12:13:90
dicosprocessor7_1 ip_addr_for_eth1 134.138.58.107

dicosprocessor8_0 eth_addr_for_eth0 00:30:f7:00:c7:b0
dicosprocessor8_0 ip_addr_for_eth0 134.138.57.108

dicosprocessor8_1 eth_addr_for_eth1 00:a0:a5:12:18:51
dicosprocessor8_1 ip_addr_for_eth1 134.138.58.108

dicosprocessor9_0 eth_addr_for_eth0 00:30:f7:00:c1:fc
dicosprocessor9_0 ip_addr_for_eth0 134.138.57.109

dicosprocessor9_1 eth_addr_for_eth1 00:a0:a5:12:13:7c
dicosprocessor9_1 ip_addr_for_eth1 134.138.58.109

dicosprocessor10_0 eth_addr_for_eth0 00:30:f7:00:c2:28
dicosprocessor10_0 ip_addr_for_eth0 134.138.57.110

dicosprocessor10_1 eth_addr_for_eth1 00:a0:a5:12:11:4c
dicosprocessor10_1 ip_addr_for_eth1 134.138.58.110

dicosprocessor11_0 eth_addr_for_eth0 00:30:f7:00:c1:c8
dicosprocessor11_0 ip_addr_for_eth0 134.138.57.111

dicosprocessor11_1 eth_addr_for_eth1 00:a0:a5:12:13:a6
dicosprocessor11_1 ip_addr_for_eth1 134.138.58.111

dicosprocessor12_0 eth_addr_for_eth0 00:30:f7:00:c2:1f
dicosprocessor12_0 ip_addr_for_eth0 134.138.57.112

dicosprocessor12_1 eth_addr_for_eth1 00:a0:a5:12:0f:4e
dicosprocessor12_1 ip_addr_for_eth1 134.138.58.112

dicosprocessor13_0 eth_addr_for_eth0 00:30:f7:00:c1:bc
dicosprocessor13_0 ip_addr_for_eth0 134.138.57.113

dicosprocessor13_1 eth_addr_for_eth1 00:a0:a5:12:13:a7
dicosprocessor13_1 ip_addr_for_eth1 134.138.58.113

dicosprocessor14_0 eth_addr_for_eth0 00:30:f7:00:c1:b3
dicosprocessor14_0 ip_addr_for_eth0 134.138.57.114

dicosprocessor14_1 eth_addr_for_eth1 00:a0:a5:12:14:4e
dicosprocessor14_1 ip_addr_for_eth1 134.138.58.114

dicosprocessor15_0 eth_addr_for_eth0 00:30:f7:00:c2:17
dicosprocessor15_0 ip_addr_for_eth0 134.138.57.115

dicosprocessor15_1 eth_addr_for_eth1 00:a0:a5:12:13:9c
dicosprocessor15_1 ip_addr_for_eth1 134.138.58.115

dicosprocessor16_0 eth_addr_for_eth0 00:30:f7:00:c1:d7
dicosprocessor16_0 ip_addr_for_eth0 134.138.57.116

dicosprocessor16_1 eth_addr_for_eth1 00:a0:a5:12:14:16
dicosprocessor16_1 ip_addr_for_eth1 134.138.58.116

dicosprocessor17_0 eth_addr_for_eth0 00:30:f7:00:c7:7d
dicosprocessor17_0 ip_addr_for_eth0 134.138.57.117

dicosprocessor17_1 eth_addr_for_eth1 00:a0:a5:12:18:4a
dicosprocessor17_1 ip_addr_for_eth1 134.138.58.117

dicosprocessor18_0 eth_addr_for_eth0 00:30:f7:00:c2:1b
dicosprocessor18_0 ip_addr_for_eth0 134.138.57.118

dicosprocessor18_1 eth_addr_for_eth1 00:a0:a5:12:13:a3
dicosprocessor18_1 ip_addr_for_eth1 134.138.58.118

dicosprocessor19_0 eth_addr_for_eth0 00:30:f7:00:c2:00
dicosprocessor19_0 ip_addr_for_eth0 134.138.57.119

dicosprocessor19_1 eth_addr_for_eth1 00:a0:a5:12:13:96
dicosprocessor19_1 ip_addr_for_eth1 134.138.58.119

dicosprocessor20_0 eth_addr_for_eth0 00:30:f7:00:c1:da
dicosprocessor20_0 ip_addr_for_eth0 134.138.57.120

dicosprocessor20_1 eth_addr_for_eth1 00:a0:a5:12:13:93
dicosprocessor20_1 ip_addr_for_eth1 134.138.58.120

dicosprocessor21_0 eth_addr_for_eth0 00:30:f7:00:c2:0d
dicosprocessor21_0 ip_addr_for_eth0 134.138.57.121

dicosprocessor21_1 eth_addr_for_eth1 00:a0:a5:12:13:a5
dicosprocessor21_1 ip_addr_for_eth1 134.138.58.121

dicosprocessor22_0 eth_addr_for_eth0 00:30:f7:00:c1:a6
dicosprocessor22_0 ip_addr_for_eth0 134.138.57.122

dicosprocessor22_1 eth_addr_for_eth1 00:a0:a5:12:13:92
dicosprocessor22_1 ip_addr_for_eth1 134.138.58.122

dicosprocessor23_0 eth_addr_for_eth0 00:30:f7:00:c1:b1
dicosprocessor23_0 ip_addr_for_eth0 134.138.57.123

dicosprocessor23_1 eth_addr_for_eth1 00:a0:a5:12:11:69
dicosprocessor23_1 ip_addr_for_eth1 134.138.58.123

dicosprocessor24_0 eth_addr_for_eth0 00:30:f7:00:c1:a2
dicosprocessor24_0 ip_addr_for_eth0 134.138.57.124

dicosprocessor24_1 eth_addr_for_eth1 00:a0:a5:12:13:94
dicosprocessor24_1 ip_addr_for_eth1 134.138.58.124

dicosprocessor25_0 eth_addr_for_eth0 00:30:f7:00:c1:b0
dicosprocessor25_0 ip_addr_for_eth0 134.138.57.125

dicosprocessor25_1 eth_addr_for_eth1 00:a0:a5:12:14:17
dicosprocessor25_1 ip_addr_for_eth1 134.138.58.125

dicosprocessor26_0 eth_addr_for_eth0 00:30:f7:00:c1:db
dicosprocessor26_0 ip_addr_for_eth0 134.138.57.126

dicosprocessor26_1 eth_addr_for_eth1 00:a0:a5:12:13:c1
dicosprocessor26_1 ip_addr_for_eth1 134.138.58.126

dicosprocessor27_0 eth_addr_for_eth0 00:30:f7:00:d6:88
dicosprocessor27_0 ip_addr_for_eth0 134.138.57.127

dicosprocessor27_1 eth_addr_for_eth1 00:a0:a5:12:13:a2
dicosprocessor27_1 ip_addr_for_eth1 134.138.58.127

dicosprocessor28_0 eth_addr_for_eth0 00:30:f7:00:d6:8b
dicosprocessor28_0 ip_addr_for_eth0 134.138.57.128

dicosprocessor28_1 eth_addr_for_eth1 00:a0:a5:12:13:86
dicosprocessor28_1 ip_addr_for_eth1 134.138.58.128

Comments:

File telorb.conf on IO processors 1 and 2, located at /opt/telorb/etc/               Back to Contents

Official template:
###################################################################
# This configuration-file specifies all data used to run telorb-related
# services on IO-machines
###################################################################

###################################################################
# define all timeservers; there may be more than one timeserver
# example:timeserver 134.138.64.26
# If both IO-machines are timeserver you should adress one through the
# first network, and the other through the second network.
###################################################################
timeserver TIMESERVER1
timeserver TIMESERVER2

###################################################################
# define the internal subnet, i.e. IO-processors and all dicosprocessors
# usually there are two internal networks
# To find out which interfaces you have and which networks are assigned
# to them type: "ifconfig -a" on you IO-machines
# Running the command on one IO-machine can give you the following output:
#  to6io1:~>ifconfig -a
#  lo0: flags=849 mtu 8232
#        inet 127.0.0.1 netmask ff000000 
#  exp0: flags=863 mtu 1500
#        inet 134.138.77.25 netmask ffffff00 broadcast 134.138.77.255
#  exp1: flags=863 mtu 1500
#        inet 134.138.33.33 netmask fffff800 broadcast 134.138.39.255
#  hme0: flags=863 mtu 1500
#        inet 134.138.187.29 netmask fffff800 broadcast 134.138.191.255
#  hme1: flags=863 mtu 1500
#        inet 134.138.76.25 netmask ffffff00 broadcast 134.138.76.255
#
# Running the same on the other IO-machine gives you enough information.
# In the following example we assume that the interface-names are the
# same on IO1 and IO2.
# internal-network subnet0 134.138.76.0
# internal-network netmask0 255.255.255.0
# internal-network defaultgw0 134.138.76.1
# internal-network bcast0 134.138.76.255
# internal-network io1net0 134.138.76.25
# internal-network io2net0 134.138.76.26
# internal-network io1interfacename0 hme1 
# internal-network io2interfacename0 hme1 
# 
# internal-network subnet1 134.138.77.0
# internal-network netmask1 255.255.255.0
# internal-network defaultgw1 134.138.77.1
# internal-network bcast1 134.138.77.255
# internal-network io1net1 134.138.77.25
# internal-network io2net1 134.138.77.26
# internal-network io1interfacename1 exp0 
# internal-network io2interfacename1 exp0 
###################################################################
internal-network subnet0 SUBNET0
internal-network netmask0 NETMASK0
internal-network defaultgw0 DEFAULTGW0
internal-network bcast0 BCAST0
internal-network io1net0 IO1NET0
internal-network io2net0 IO2NET0
internal-network io1interfacename0 IO1INTERFACENAME0
internal-network io2interfacename0 IO2INTERFACENAME0

internal-network subnet1 SUBNET1
internal-network netmask1 NETMASK1
internal-network defaultgw1 DEFAULTGW1
internal-network bcast1 BCAST1
internal-network io1net1 IO1NET1
internal-network io2net1 IO2NET1
internal-network io1interfacename1 IO1INTERFACENAME1
internal-network io2interfacename1 IO2INTERFACENAME1

###################################################################
# define how to boot the dicosprocessors
# use SMALLPROM or PXE
###################################################################
booting SMALLPROM
#booting PXE

###################################################################
# define dump-server ip-address
# If both IO-machines are dump-server you should adress one through the
# first network, and the other through the second network.
###################################################################
dumpserverip DUMPSERVERIP1
dumpserverip DUMPSERVERIP2

###################################################################
# define console-server ip-address
###################################################################
consserverip CONSSERVERIP1

###################################################################
# define first port for terminal-server
# e.g. tsport 7001
###################################################################
tsport TSPORT

###################################################################
# define all dicosprocessors
#
# define the mac-address and ip-address
# if the processor shall be a loader you have to add the third
# line that defines the network through which loading takes
# place
#
# example:
# dicosprocessor1_0 eth_addr_for_eth0 00:80:50:01:4d:d1
# dicosprocessor1_0 ip_addr_for_eth0 134.138.63.101
# dicosprocessor1_0 eptftp_server_net0
#
###################################################################
dicosprocessor1_0 eth_addr_for_eth0 ETH_ADDR_FOR_ETH
dicosprocessor1_0 ip_addr_for_eth0 IP_ADDR_FOR_ETH
dicosprocessor1_0 eptftp_server_net0

dicosprocessor1_1 eth_addr_for_eth1 ETH_ADDR_FOR_ETH
dicosprocessor1_1 ip_addr_for_eth1 IP_ADDR_FOR_ETH
dicosprocessor1_1 eptftp_server_net1

###################################################################
# this processor is not a loader because eptftp_server_net0 is
# commented out
###################################################################
dicosprocessor2_0 eth_addr_for_eth0 ETH_ADDR_FOR_ETH
dicosprocessor2_0 ip_addr_for_eth0 IP_ADDR_FOR_ETH
#dicosprocessor2_0 eptftp_server_net0

dicosprocessor2_1 eth_addr_for_eth1 ETH_ADDR_FOR_ETH
dicosprocessor2_1 ip_addr_for_eth1 IP_ADDR_FOR_ETH
#dicosprocessor2_1 eptftp_server_net1

dicosprocessor3_0 eth_addr_for_eth0 ETH_ADDR_FOR_ETH
dicosprocessor3_0 ip_addr_for_eth0 IP_ADDR_FOR_ETH
#dicosprocessor3_0 eptftp_server_net0

dicosprocessor3_1 eth_addr_for_eth1 ETH_ADDR_FOR_ETH
dicosprocessor3_1 ip_addr_for_eth1 IP_ADDR_FOR_ETH
#dicosprocessor3_1 eptftp_server_net1

Comments:

File telorb.conf on IO processors 1 and 2, located at /opt/telorb/etc/               Back to Contents

Official example:
###################################################################
# This configuration-file specifies all data used to run telorb-related
# services on IO-machines
###################################################################

###################################################################
# define all timeservers; there may be more than one timeserver
# example:timeserver 134.138.77.26
# If both IO-machines are timeserver you should adress one through the
# first network, and the other through the second network.
###################################################################
timeserver 134.138.76.25
timeserver 134.138.77.26

###################################################################
# define the internal subnet, i.e. IO-processors and all dicosprocessors
# usually there are two internal networks
# To find out which interfaces you have and which networks are assigned
# to them type: "ifconfig -a" on you IO-machines
# Running the command on one IO-machine can give you the following output:
#  to6io1:~>ifconfig -a
#  lo0: flags=849 mtu 8232
#        inet 127.0.0.1 netmask ff000000 
#  exp0: flags=863 mtu 1500
#        inet 134.138.77.25 netmask ffffff00 broadcast 134.138.77.255
#  exp1: flags=863 mtu 1500
#        inet 134.138.33.33 netmask fffff800 broadcast 134.138.39.255
#  hme0: flags=863 mtu 1500
#        inet 134.138.187.29 netmask fffff800 broadcast 134.138.191.255
#  hme1: flags=863 mtu 1500
#        inet 134.138.76.25 netmask ffffff00 broadcast 134.138.76.255
#
# Running the same on the other IO-machine gives you enough information.
# In the following example we assume that the interface-names are the
# same on IO1 and IO2.
###################################################################
internal-network subnet0 134.138.76.0
internal-network netmask0 255.255.255.0
internal-network defaultgw0 134.138.76.1
internal-network bcast0 134.138.76.255
internal-network io1net0 134.138.76.25
internal-network io2net0 134.138.76.26
internal-network io1interfacename0 hme1 
internal-network io2interfacename0 hme1 

internal-network subnet1 134.138.77.0
internal-network netmask1 255.255.255.0
internal-network defaultgw1 134.138.77.1
internal-network bcast1 134.138.77.255
internal-network io1net1 134.138.77.25
internal-network io2net1 134.138.77.26
internal-network io1interfacename1 exp0 
internal-network io2interfacename1 exp0 

###################################################################
# define how to boot the dicosprocessors
# use SMALLPROM or PXE
###################################################################
booting SMALLPROM
#booting PXE

###################################################################
# define dump-server ip-address
# If both IO-machines are dump-server you should adress one through the
# first network, and the other through the second network.
###################################################################
dumpserverip 134.138.76.25
dumpserverip 134.138.77.26

###################################################################
# define console-server ip-address
###################################################################
consserverip 134.138.76.25

###################################################################
# define first port for terminal-server
# e.g. tsport 7001
###################################################################
tsport 7001

###################################################################
# define all dicosprocessors, i.e. define the mac-address,
# ip-address
#
# if the processor shall be a loader the ip-address for the tftp-server
# has to be added (dicosprocessor1_0 eptftp_server_net0)
###################################################################
dicosprocessor1_0 eth_addr_for_eth0 00:80:50:01:4d:8b
dicosprocessor1_0 ip_addr_for_eth0 134.138.76.101
dicosprocessor1_0 eptftp_server_net0

dicosprocessor1_1 eth_addr_for_eth1 00:80:50:01:5d:9a
dicosprocessor1_1 ip_addr_for_eth1 134.138.77.101
dicosprocessor1_1 eptftp_server_net1

dicosprocessor2_0 eth_addr_for_eth0 00:80:50:00:c9:9b
dicosprocessor2_0 ip_addr_for_eth0 134.138.76.102
dicosprocessor2_0 eptftp_server_net0

dicosprocessor2_1 eth_addr_for_eth1 00:80:50:00:8a:39
dicosprocessor2_1 ip_addr_for_eth1 134.138.77.102
dicosprocessor2_1 eptftp_server_net1

dicosprocessor3_0 eth_addr_for_eth0 00:80:50:00:ce:d1
dicosprocessor3_0 ip_addr_for_eth0 134.138.76.103

dicosprocessor3_1 eth_addr_for_eth1 00:80:50:00:96:bd
dicosprocessor3_1 ip_addr_for_eth1 134.138.77.103

dicosprocessor4_0 eth_addr_for_eth0 00:80:50:00:c9:9c
dicosprocessor4_0 ip_addr_for_eth0 134.138.76.104

dicosprocessor4_1 eth_addr_for_eth1 00:80:50:00:8a:45
dicosprocessor4_1 ip_addr_for_eth1 134.138.77.104

dicosprocessor5_0 eth_addr_for_eth0 00:80:50:00:c9:90
dicosprocessor5_0 ip_addr_for_eth0 134.138.76.105

dicosprocessor5_1 eth_addr_for_eth1 00:80:50:00:8a:3d
dicosprocessor5_1 ip_addr_for_eth1 134.138.77.105

dicosprocessor6_0 eth_addr_for_eth0 00:80:50:00:c9:9f
dicosprocessor6_0 ip_addr_for_eth0 134.138.76.106

dicosprocessor6_1 eth_addr_for_eth1 00:80:50:00:8a:3a
dicosprocessor6_1 ip_addr_for_eth1 134.138.77.106

dicosprocessor7_0 eth_addr_for_eth0 00:80:50:00:c9:71
dicosprocessor7_0 ip_addr_for_eth0 134.138.76.107

dicosprocessor7_1 eth_addr_for_eth1 00:80:50:00:8a:3e
dicosprocessor7_1 ip_addr_for_eth1 134.138.77.107

Comments:

File S88TelorbServices on IO processors 1 and 2, located at /etc/rc3.d/               Back to Contents

Example of file contents:
#!/bin/sh
# start/stop/restart all telorb-related services

#set -x

usage="Usage: /etc/rc3.d/S88TelorbServices start|stop|restart"

if [ ! -d /opt/telorb/etc ]
then                    # /opt/telorb/tools/bin not mounted
        exit
fi

# Start/stop/restart the telorb services start script
if [ $# -eq 1 ] ; then
  case "$1" in
     'start')

        if [ -f /opt/telorb/etc/start_services ] ; then
                su telorb -c /opt/telorb/etc/start_services
        fi
        ;;

     'stop')

        if [ -f /opt/telorb/etc/stop_services ] ; then
                su telorb -c /opt/telorb/etc/stop_services
        fi
        ;;

     'restart')

        if [ -f /opt/telorb/etc/stop_services ] ; then
                su telorb -c /opt/telorb/etc/stop_services
        fi
        if [ -f /opt/telorb/etc/start_services ] ; then
                su telorb -c /opt/telorb/etc/start_services
        fi
        ;;

     *)
        echo $usage;;
  esac
else
  echo $usage
fi

Comments:

File start_services on IO processor 1, located at /opt/telorb/etc/               Back to Contents

Example of file contents:
#!/bin/csh
source /opt/telorb/codearchive/Unix_IDP/env/setup.csh

setenv DUMPDIR /opt/telorb/dumps

# Cleanup old mess
rm -rf /tmp/FileServerInterpreter.pid
rm -rf /tmp/DUCK-server-subscr.socket
rm -rf /tmp/DUCK-server.pid
rm -rf /tmp/DUCK-server.socket

# Settings for the file server
#rm -f /tmp/axe/*
setenv DICOS_FILESYSTEM_ROOT /opt/telorb/axe

## Start the telorb services

/opt/telorb/codearchive/Unix_IDP/DUCKServer_LM/scripts/DUCK-server.io.csh  -th 134.138.57.101 -th 134.138.57.102 -hbt 10 -hbi 5 -rci 5&


/opt/telorb/codearchive/Unix_IDP/EpTftpd_LM/scripts/ep_tftpd.io.csh /opt/telorb/etc/ep_tftpd.conf&

/opt/telorb/codearchive/Unix_IDP/FileServerInterpreter_LM/scripts/FileServerInterpreter.io.csh -n io1&

# Start the dump daemon
/opt/telorb/codearchive/Unix_IDP/TftpDumpd_LM/scripts/dumpd.io.csh -s $DUMPDIR -i &


# Example
#/opt/telorb/codearchive/Unix_IDP/STSsw_LM/scripts/STSsw.io.csh 7 7001 -log &

/opt/telorb/codearchive/Unix_IDP/STSsw_LM/scripts/STSsw.io.csh 28 7001 -log &


/opt/telorb/codearchive/Unix_IDP/DicosSyslogClient_LM/scripts/DicosSyslogClient.io.csh -L -d 5 -m io1 -t 134.138.57.101-128  &

Comments:

File start_services on IO processor 2, located at /opt/telorb/etc/               Back to Contents

Example of file contents:
#!/bin/csh
source /opt/telorb/codearchive/Unix_IDP/env/setup.csh

setenv DUMPDIR /opt/telorb/dumps

# Cleanup old mess
rm -rf /tmp/FileServerInterpreter.pid
rm -rf /tmp/DUCK-server-subscr.socket
rm -rf /tmp/DUCK-server.pid
rm -rf /tmp/DUCK-server.socket

# Settings for the file server
#rm -f /tmp/axe/*
setenv DICOS_FILESYSTEM_ROOT /opt/telorb/axe

## Start the telorb services

/opt/telorb/codearchive/Unix_IDP/DUCKServer_LM/scripts/DUCK-server.io.csh -th 134.138.58.101 -th 134.138.58.102 -hbt 10 -hbi 5 -rci 5&


/opt/telorb/codearchive/Unix_IDP/EpTftpd_LM/scripts/ep_tftpd.io.csh /opt/telorb/etc/ep_tftpd.conf&

/opt/telorb/codearchive/Unix_IDP/FileServerInterpreter_LM/scripts/FileServerInterpreter.io.csh -n io2&

# Start the dump daemon
/opt/telorb/codearchive/Unix_IDP/TftpDumpd_LM/scripts/dumpd.io.csh -s $DUMPDIR -i &


/opt/telorb/codearchive/Unix_IDP/DicosSyslogClient_LM/scripts/DicosSyslogClient.io.csh -L -d 5 -m io2 -t 134.138.58.101-128  &

Comments:

File ep_tftpd.conf on IO processor 1, located at /opt/telorb/etc/               Back to Contents

Example of file contents:
# Ip Address   Absoulte path to the bootload table for the lprocessor to load    Loading group name
134.138.57.101 /opt/telorb/axe/loadingGroup01_1/Processor1/bootLoadTable.0       loadingGroup01_1
134.138.58.101 /opt/telorb/axe/loadingGroup01_1/Processor1/bootLoadTable.0       loadingGroup01_1
134.138.57.102 /opt/telorb/axe/loadingGroup01_1/Processor2/bootLoadTable.0       loadingGroup01_1
134.138.58.102 /opt/telorb/axe/loadingGroup01_1/Processor2/bootLoadTable.0       loadingGroup01_1

Comments:

File ep_tftpd.conf on IO processor 2, located at /opt/telorb/etc/               Back to Contents

Example of file contents:
# Ip Address   Absoulte path to the bootload table for the lprocessor to load    Loading group name
134.138.57.101 /opt/telorb/axe/loadingGroup01_2/Processor1/bootLoadTable.0       loadingGroup01_2
134.138.58.101 /opt/telorb/axe/loadingGroup01_2/Processor1/bootLoadTable.0       loadingGroup01_2
134.138.57.102 /opt/telorb/axe/loadingGroup01_2/Processor2/bootLoadTable.0       loadingGroup01_2
134.138.58.102 /opt/telorb/axe/loadingGroup01_2/Processor2/bootLoadTable.0       loadingGroup01_2

Comments:

File networkAddresses on IO processors 1 and 2, located at /opt/telorb/axe/loadingGroup01_X/               Back to Contents

Example of file contents:
1 1 00:30:f7:00:c1:bd 00:a0:a5:12:13:88
1 2 00:30:f7:00:c7:65 00:a0:a5:12:11:34
1 3 00:30:f7:00:c7:8f 00:a0:a5:12:17:d3
1 4 00:30:f7:00:c1:e9 00:a0:a5:12:11:35
1 5 00:30:f7:00:c1:dc 00:a0:a5:12:11:4a
1 6 00:30:f7:00:c7:69 00:a0:a5:12:11:15
1 7 00:30:f7:00:c5:89 00:a0:a5:12:13:90
1 8 00:30:f7:00:c7:b0 00:a0:a5:12:18:51
1 9 00:30:f7:00:c1:fc 00:a0:a5:12:13:7c
1 10 00:30:f7:00:c2:28 00:a0:a5:12:11:4c
1 11 00:30:f7:00:c1:c8 00:a0:a5:12:13:a6
1 12 00:30:f7:00:c2:1f 00:a0:a5:12:0f:4e
1 13 00:30:f7:00:c1:bc 00:a0:a5:12:13:a7
1 14 00:30:f7:00:c1:b3 00:a0:a5:12:14:4e
1 15 00:30:f7:00:c2:17 00:a0:a5:12:13:9c
1 16 00:30:f7:00:c1:d7 00:a0:a5:12:14:16
1 17 00:30:f7:00:c7:7d 00:a0:a5:12:18:4a
1 18 00:30:f7:00:c2:1b 00:a0:a5:12:13:a3
1 19 00:30:f7:00:c2:00 00:a0:a5:12:13:96
1 20 00:30:f7:00:c1:da 00:a0:a5:12:13:93
1 21 00:30:f7:00:c2:0d 00:a0:a5:12:13:a5
1 22 00:30:f7:00:c1:a6 00:a0:a5:12:13:92
1 23 00:30:f7:00:c1:b1 00:a0:a5:12:11:69
1 24 00:30:f7:00:c1:a2 00:a0:a5:12:13:94
1 25 00:30:f7:00:c1:b0 00:a0:a5:12:14:17
1 26 00:30:f7:00:c1:db 00:a0:a5:12:13:c1

Comments:

File to14_cons_io1, located at e.g.  /home/telorb/to14/consolelogs/               Back to Contents

Example of file contents:
#! /bin/sh

xterm -ls -sb -fn 8x13 -geometry 72x12+40+0    -sl 500 -title "Processor1" -e tcsh -c 'telnet to14io1 7001' &
xterm -ls -sb -fn 8x13 -geometry 72x12+660+0   -sl 500 -title "Processor2" -e tcsh -c 'telnet to14io1 7002' &
xterm -ls -sb -fn 8x13 -geometry 72x12+40+200  -sl 500 -title "Processor3" -e tcsh -c 'telnet to14io1 7003' &
xterm -ls -sb -fn 8x13 -geometry 72x12+660+200 -sl 500 -title "Processor4" -e tcsh -c 'telnet to14io1 7004' &
xterm -ls -sb -fn 8x13 -geometry 72x12+40+400  -sl 500 -title "Processor5" -e tcsh -c 'telnet to14io1 7005' &
xterm -ls -sb -fn 8x13 -geometry 72x12+660+400 -sl 500 -title "Processor6" -e tcsh -c 'telnet to14io1 7006' &
xterm -ls -sb -fn 8x13 -geometry 72x12+40+600  -sl 500 -title "Processor7" -e tcsh -c 'telnet to14io1 7007' &
xterm -ls -sb -fn 8x13 -geometry 72x12+660+600 -sl 500 -title "Processor8" -e tcsh -c 'telnet to14io1 7008' &
xterm -ls -sb -fn 8x13 -geometry 72x12+40+800  -sl 500 -title "Processor9" -e tcsh -c 'telnet to14io1 7009' &
xterm -ls -sb -fn 8x13 -geometry 72x12+660+800 -sl 500 -title "Processor10" -e tcsh -c 'telnet to14io1 7010' &
xterm -ls -sb -fn 8x13 -geometry 72x12+40+0    -sl 500 -title "Processor11" -e tcsh -c 'telnet to14io1 7011' &
xterm -ls -sb -fn 8x13 -geometry 72x12+660+0   -sl 500 -title "Processor12" -e tcsh -c 'telnet to14io1 7012' &
xterm -ls -sb -fn 8x13 -geometry 72x12+40+200  -sl 500 -title "Processor13" -e tcsh -c 'telnet to14io1 7013' &
xterm -ls -sb -fn 8x13 -geometry 72x12+660+200 -sl 500 -title "Processor14" -e tcsh -c 'telnet to14io1 7014' &
xterm -ls -sb -fn 8x13 -geometry 72x12+40+400  -sl 500 -title "Processor15" -e tcsh -c 'telnet to14io1 7015' &
xterm -ls -sb -fn 8x13 -geometry 72x12+660+400 -sl 500 -title "Processor16" -e tcsh -c 'telnet to14io1 7016' &
xterm -ls -sb -fn 8x13 -geometry 72x12+40+600  -sl 500 -title "Processor17" -e tcsh -c 'telnet to14io1 7017' &
xterm -ls -sb -fn 8x13 -geometry 72x12+660+600 -sl 500 -title "Processor18" -e tcsh -c 'telnet to14io1 7018' &
xterm -ls -sb -fn 8x13 -geometry 72x12+40+800  -sl 500 -title "Processor19" -e tcsh -c 'telnet to14io1 7019' &
xterm -ls -sb -fn 8x13 -geometry 72x12+660+800 -sl 500 -title "Processor20" -e tcsh -c 'telnet to14io1 7020' &
xterm -ls -sb -fn 8x13 -geometry 72x12+40+0    -sl 500 -title "Processor21" -e tcsh -c 'telnet to14io1 7021' &
xterm -ls -sb -fn 8x13 -geometry 72x12+660+0   -sl 500 -title "Processor22" -e tcsh -c 'telnet to14io1 7022' &
xterm -ls -sb -fn 8x13 -geometry 72x12+40+200  -sl 500 -title "Processor23" -e tcsh -c 'telnet to14io1 7023' &
xterm -ls -sb -fn 8x13 -geometry 72x12+660+200 -sl 500 -title "Processor24" -e tcsh -c 'telnet to14io1 7024' &
xterm -ls -sb -fn 8x13 -geometry 72x12+40+400  -sl 500 -title "Processor25" -e tcsh -c 'telnet to14io1 7025' &
xterm -ls -sb -fn 8x13 -geometry 72x12+660+400 -sl 500 -title "Processor26" -e tcsh -c 'telnet to14io1 7026' &
xterm -ls -sb -fn 8x13 -geometry 72x12+40+600  -sl 500 -title "Processor27" -e tcsh -c 'telnet to14io1 7027' &
xterm -ls -sb -fn 8x13 -geometry 72x12+660+600 -sl 500 -title "Processor28" -e tcsh -c 'telnet to14io1 7028' &
xterm -ls -sb -fn 8x13 -geometry 72x12+40+800  -sl 500 -title "Processor29" -e tcsh -c 'telnet to14io1 7029' &
xterm -ls -sb -fn 8x13 -geometry 72x12+660+800 -sl 500 -title "Processor30" -e tcsh -c 'telnet to14io1 7030' &

File README.txt, located at e.g.  /home/telorb/to14/consolelogs/               Back to Contents

Example of file contents:
How to start the magic consolelogs that never grows beyond 2 Megs in size.

Example:

./indstartlog 28 7001 to14io1

File .telnetrc, located at e.g.  /home/telorb/ on the local network               Back to Contents

Example of file contents:
# command lines must begin with a whitespace
to1ts1 
        unset interrupt
to1ts2 
        unset interrupt
to1ts3 
        unset interrupt
to1ts4 
        unset interrupt
to1ts5 
        unset interrupt
to1ts
        unset interrupt
to2ts
        unset interrupt
to3ts
        unset interrupt
to4ts
        unset interrupt
to5ts
        unset interrupt
to6ts
        unset interrupt
to7ts        
        unset interrupt
to8ts        
        unset interrupt
to9ts        
        unset interrupt
to10ts       
        unset interrupt
to11ts       
        unset interrupt
to12ts       
        unset interrupt
to13ts       
        unset interrupt
to14ts       
        unset interrupt
to15ts       
        unset interrupt
to1io1        
        unset interrupt
to2io1        
        unset interrupt
to3io1        
        unset interrupt
to4io1        
        unset interrupt
to5io1        
        unset interrupt
to6io1        
        unset interrupt
to7io1        
        unset interrupt
to8io1        
        unset interrupt
to9io1        
        unset interrupt
to10io1        
        unset interrupt
to11io1        
        unset interrupt
to12io1        
        unset interrupt
to13io1        
        unset interrupt
to14io1        
        unset interrupt
to15io1        
        unset interrupt
to100io1
        unset interrupt
to101io1
        unset interrupt
teodor1
        unset interrupt
 
Created by
UAB/S/DV Michel Sundin
  Date
February 22, 2001
  Visits
Counter
 

http://uabweb.uab.ericsson.se/inside/units/k/kh/d/dv/document/guidelines/files_ad13.html